Conversation
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 introduces a new
ERBYieldNodenode so can more specifically targetyieldcalls in ERB files, which usually need to be handled specially.Since we extract the Ruby code from the source input we have a
yieldcall in the a top-level of the Ruby source, which is not valid and results in a syntax error.Given this file:
We get this Ruby source:
yield :headWhich is not valid Ruby and results in this Prism error:
Parse Tree (before):
Since
yieldcalls are commonly used in ERB we are going to ignore theinvalid_yieldPrism parse error for now.Parse Tree (after merging this pull request):
Which now includes the
ERBYieldNodenode and doesn't have theinvalid_yieldRubyParseError.Resolves #90