Parser: Allow inline case/when and case/in in strict mode#1263
Merged
Conversation
ff7c751 to
e8639e9
Compare
e8639e9 to
1021d3a
Compare
1021d3a to
9f9a9e5
Compare
commit: |
🌿 Interactive Playground and Documentation PreviewA preview deployment has been built for this pull request. Try out the changes live in the interactive playground: 🌱 Grown from commit ✅ Preview deployment has been cleaned up. |
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 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.
This pull request updates the parser to provide backwards compatibility for
<% case @foo when :bar %>(case/whenorcase/inin a single ERB tag) by gating theERBCaseWithConditionsErrorbehind strict mode.This syntax is valid Erubi and, for backwards compatibility reasons, we should also make this also work in Herb. With this change, non-strict now mode accepts this syntax and now correctly compiles it by splitting a the single ERB Node into multiple AST nodes by creating a new synthetic
ERBWhenNodeorERBCaseInNodenode.The following template:
Now gets parsed as this in non-strict mode:
In strict mode it will still produce a
ERBCaseWithConditionsError.Before this change, it was parsed as:
Resolves #1252
Related #1112