Fix enable-jinja2-autoescape when kwargs can't be known
#397
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
clavedeluna
approved these changes
Mar 19, 2024
| expexted_output | ||
| ) = """ | ||
| import jinja2 | ||
| env = jinja2.Environment(**kwargs) |
There was a problem hiding this comment.
I would've thought a more telling test case would be
env = jinja2.Environment(**{"autoescape": True}) but I think it will trigger in all cases.
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Overview
Fix
enable-jinja2-autoescapewhen kwargs can't be knownDescription
**kwargscan't be knownautoescapein this case and it's already present inkwargsthen we are going to break the code