-
Notifications
You must be signed in to change notification settings - Fork 1.5k
WIP #2017
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: v6
Are you sure you want to change the base?
WIP #2017
Conversation
cf8f143 to
07531a7
Compare
07531a7 to
c12fc1b
Compare
karreiro
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for this PR, @charlespwd! Great stuff! I've left some comments that may be applied in follow-up PRs.
karreiro
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the changes, @charlespwd!
| * As tag argument `{% render 'snip', enabled: a or b %}` | ||
| * As conditional tag argument `{% if cond %}` (extending previous behaviour) | ||
| * (TODO) Add support for subexpression prioritization and associativity | ||
| * In ascending order of priority: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is not missing from this list?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Deep pull :D It's not in scope (yet?), but, unlike last time, we wouldn't be held back by lax anymore and the system would leave space for a UnaryExpression node with an operator and an expression.
Reviewers, please note base branch to PR.
In this PR
Environment.error_modelax_parse,strict_parse+:warnerror modestrict2_parsetoparse_markupwarningssystem