Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
When using the
in
operator inside a template literal, if the object is null, compiler will fail.For example:
{{ 'yes' if myOption in preferences else 'no' }}
fails to render ifpreferences
is not in context map.In Python's Jinja2 render, it is possible to setup the compiler to make this render to
no
.I would expect this not to fail if
throwOnUndefined
is set to false. If this is not the expected behavior, would like to hear what would be the option to support this.Also would like to add a test for this but I am not sure what would be the correct location.
This PR fixes the compiler issue.
Checklist
I've completed the checklist below to ensure I didn't forget anything. This makes reviewing this PR as easy as possible for the maintainers. And it gets this change released as soon as possible.