6.0.0 Breaking change: parser.parse() -> parse() with better error message #53
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 change adds a new API to access the
parsefunction directly rather than import the parser. The README has been updated in this branch to reflect the change.Old way to parse:
New way to parse:
parser.parse()exposes aGlslSyntaxErrorwhich is an alias forpeggy.SyntaxError- the raw error from the Peggy parser. This error has a painful, confusingformat()method that should not be exposed to end users.When using
parse()- it wraps the error in one that automatically formats it, hiding thegrammarSourceWhen using
parse()instead ofparser.parse(), if you're checking the error type in a parse catch block. Old code:New code:
Also if you were importing the error type, you need to update your code to import the class instance
New code: