Fix grammar: allow import between rules and complex expression in else statement #80
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
Signed-off-by: Vincent Gramer <[email protected]>
also merge 'else keyword' and 'else keyword 2' tests into 'else keyword' Signed-off-by: Vincent Gramer <[email protected]>
vgramer
force-pushed
the
fix_grammar_import_else
branch
from
a710c75 to
0de7b98
Compare
vgramer
requested review from
irodzik,
anderseknert,
asadali,
frankiecerk and
lkadalski
vgramer
added
area/grammar
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.
Description
Fix grammar to:
policy.expr2instead oftermgrammar rule in else statementrelease notes
Fixes #76
Fixes #78
Special notes for your reviewer
'else keyword' and 'else keyword 2' tests have been merged into 'else keyword' test