-
Notifications
You must be signed in to change notification settings - Fork 43
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
fix(parse): Restore nested block parsing #514
Conversation
aa1d858
to
176d71f
Compare
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.
Awesome, looks great!
throw addError(peek(), "Expected 'end if' to terminate 'else' block"); | ||
} | ||
elseBranch = maybeElseBranch.body; | ||
endIfToken = maybeElseBranch.closingToken; |
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.
Ooh nice does this mean the endIfToken
is populated now? I ran into this when I was writing the coverage tool
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.
It does! That's where a few of the snapshot updates came into play 😃
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.
Same questions as Levi but this is great stuff!
I'd accidentally broken nested-block parsing in #510! This fixes that and ensures that `block()` always consumes the block-closing token.
176d71f
to
b041596
Compare
I'd accidentally broken nested-block parsing in #510! This fixes that and ensures that
block()
always consumes the block-closing token.