Json encode twig variables

[LucaGallinari]

It's safer and better to use the json encoder for all variables that are passed to twig files

[lruozzi9]

Is ti possible to encode parameters before passing them to twig? Instead of adding so many json_encode and raw filters?

[LucaGallinari]

We could do that, but the only advantage of that is that we have clean templates, beside this there will be only cons:

• It would be bit tricky to implement conditions in twig (if/else) cause the data will be json encoded. Examples: string will have double double quotes (like ""search term"" instead of "search term"), some characters will have escape chars etc.
• Array and objects should not be encoded when passing them to the templates otherwise you will lose the ability to perform if/for on the template. This way you will still have to do the |json_encode|raw in templates for these values.
• Given the two above you would have some template parameters encoded to json and some not encoded.... this is horrible. Encoding should be done only in "one point", in the PHP logic or in the template.

The best solution that i can think of is that we should not "compose" the json ourself but it should be encoded via a single json_encode from a single PHP array/object: to do this we should transform all "yaml templates" to "php templates" that return an array/object. But this requires a bit of rewriting.

[lruozzi9]

The best solution that i can think of is that we should not "compose" the json ourself but it should be encoded via a single json_encode from a single PHP array/object: to do this we should transform all "yaml templates" to "php templates" that return an array/object. But this requires a bit of rewriting.

The goal of having JSON files is to write queries in the same syntax as Elasticsearch (see https://www.mon-code.net/post/125/use-elasticsearch-with-symfony-framework-and-elasticsearch-php-library#:~:text=Symfony%20debug%20Toolbar.-,Using%20Twig,-All%20queries%20need). Probably it is ok for now.