dropping backward compatibility in the antlr parser#1173
Merged
Conversation
Janther
force-pushed
the
drop-backward-compatibility
branch
from
69cfe1f to
75904f0
Compare
Janther
force-pushed
the
drop-backward-compatibility
branch
from
75904f0 to
9cad3a0
Compare
fvictorio
approved these changes
Jun 23, 2025
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
2 participants
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 was kept while the
slangparser was still being developed. Now that it is our main parser and forces prettier's version to be^3.0.0there's no need for this anymore.Also on this PR the
path.getNode()was replaced bypath.node, andpath.getParentNode()bypath.parent, since this behaviour was created on[email protected].