jinja2 autoescape codemod should allow for setting autoescape to select_autoescape
callable
#285
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.
Description
autoescape=select_autoescape(...)
is the encouraged way in the jinja2 docs:True
, but that is more difficult than it sounds due to branch analysis.aiohttp_jinja2.setup
default forautoescape
as also being default of False, however, it's actually the secure value of True. I thought maybe that was a recent change but not so, it's been there for a while since v0.15aiohttp_jinja2.setup
and also allowed it to acceptjinja2.select_autoescape
since the docs state this is passed directly to jinja's Environment classCloses #284