Charles d'Avernas

@fjtirado as discussed in PM, I totally understand your point of view, which is documented insightfully by others in the issue shared by @gibson042 (thank you!). As I have never...

> when defining the workflow in json. Well, why would you go through the sheer pain of defining anything in JSON when you can do it in YAML, I wonder?

> Believe or not, for me is easier to use {} (json) than tabs (yaml) I believe you, and that's your right. But I am convinced that it will probably...

@ricardozanini @JBBianchi @gibson042 @jorgenj WDYT?

> Ok, it seems we have an agreement. Once @cdavernas is done with the DSL refactor, I will open a PR associated to this issue modifying the spec and the...

AFAIK, in YAML you do not have to do anything, because happilly it starts with ${, not simply {. The reasoning behind using mustaches, which people can understandingly be nervous...

> In YAML you need to either use white spaces or quoutes, since { and } are special characters that needs to be esscaped This is valid, with no quotes,...

> I agree we can wait till next week, I was raising the point becuase there is another PR where the ${} appeared (the looss evaluation one) and we need...

> should not be (if it is, maybe the parser you are using is smart and intepreting that {} are not special characted but part of the string because the...

> But I would be happy if you point me to the specification section of yaml when thats stated so we can be sure that ${ working without qoutes is...