Reintroduce operator precedence fix with legacy override #902
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
Still figuring out exactly what this is to find a name for it.
|
Actually, I want to move some of the tests around first. |
jasmith-hs
approved these changes
Jul 28, 2022
Comment on lines
+643
to
+646
| @FunctionalInterface | ||
| private interface ParseLevel { | ||
| AstNode apply(boolean required) throws ScanException, ParseException; | ||
| } |
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.
Closes #893
This PR is basically #895 but with the changes disabled by default. They can be enabled by setting a new flag on
LegacyOverridesas part of theJinjavaConfig.