Re: [openstack-dev] [Mistral] Changing "expression" delimiters in Mistral DSL

2015-02-17 Thread Patrick Hoolboom
My main concern with the {} delimiters in YAQL is that the curly brace already has a defined use within YAML. We most definitely will eventually run in to parsing errors with whatever delimiter we choose but I don't feel that it should conflict with the markup language it is directly embedded in.

Re: [openstack-dev] [Mistral] Changing "expression" delimiters in Mistral DSL

2015-02-18 Thread Patrick Hoolboom
mbracing quotes needed like in Ansible so no ambiguity on data types). > > The secondary criteria is syntax symmetry. After all I agree with > Patrick's point about better readability when we have opening and closing > sequences alike. > > Some additional details can be found in [0]