v1.20.0: Before opening a "bug" for Ansible-Jinja parsing.

[SteveRodrigue]

We just had to revert back YAML to 1.19.1 in VScode, because the ansible-jinja parsing was broken.
In VScode. ansible-jinja would be full of YAML parsing errors. Reverting to YAML 1.19.1 fixed the problem.

I feel like 1.20.0 breaks the interaction with Ansible 26.1.3.

Does anyone else have the same problem? We aren't sure if it could be caused by a parameter of ours. So, if others have the same ansible-jinja errors, we will try to properly document the issue.

[SteveRodrigue]

This bug:
#1204

Conversation closed.