Multiple Suggestion: Add yaml support via json-yaml equivalence, variable decorators

[jptalukdar]

Since JPL already supports json, supporting yaml shouldn't be a issue.

For example, the following json can be converted to yaml to get rid of the braces for the python folks

[
  { "let": { "name": "JSON", "times": 3 } },
  {
    "for": {
      "var": "i",
      "from": 1,
      "to": "times",
      "do": [
        { "print": { "add": ["Hello ", "name"] } }
      ]
    }
  }
]

is equivalent to

- let:
    name: JSON
    times: 3
- for:
    var: i
    from: 1
    to: times
    do:
      - print:
          add:
            - 'Hello '
            - name

If you detect a yaml, check if you can convert to a json. If not say this yaml is not supported.

secondly, there isn't any difference between a variable or a string. One suggestion would be to consider everything as a string and perform string templating either via markers such as $var_name or {{ var_name }} [Jinja style] or " { var_name } " [Java Template style]

This would make the language even more powerful

[kapilkumar9976]

Hey, thanks for the amazing, detailed feedback. I love it

Yes, YAML should be supported; converting YAML to JSON is easy, and also parsing YAML directly won't be that hard. I'm planning it, and next week, a new release is planned with all the feedback, suggestions and feature requests it'll get.
Also, for the data type, I'm thinking of adding support for basic data types such as numbers and strings, as currently, everything is a string. Moreover, your idea is amazing.

One suggestion would be to consider everything as a string and perform string templating either via markers such as $var_name or {{ var_name }} [Jinja style] or " { var_name } " [Java Template style]

This looks very cool. This will be implemented in the new release.