Allow +%} to ignore trim_blocks#1240
Merged
davidism merged 1 commit intopallets:masterfrom Jun 22, 2020
Merged
Conversation
septatrix
reviewed
Jun 22, 2020
fd9beec to
6b01227
Compare
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Resolves #1036
Summary:
trim_blockis enabled and a block ends with+%}or+#}, the behavior will be ignored.{% raw +%}will raise an error) because they don't process the inner text+%}is still allowed whentrim_blockis disabled but exhibits NOP behaviortrim_blockis enabled:results in
Tests:
test_lexnparse.pyTestTrimBlocksTrimLstripBlocksFiles affected:
lexer.pytest_lexnparse.py