Repository navigation
feat: AnalogParserErrorListener for both parser and lexer - #122
Merged
Merged
Conversation
…into error_listener
…e case where syntaxError is given None as argument `e` by adding GenericAnalogParserError, changed error_message_formatter to use always make use of custom message.
yhteoh
changed the title
yhteoh
changed the title
yhteoh
marked this pull request as ready for review
October 28, 2026 14:15
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.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
feature
What is the current behavior? (You can also link to an open issue here)
parsing and lexing uses default behavior from
antlr, errors are not raisedWhat is the new behavior (if this is a feature change)?
AnalogParserErrorListenerinheriting from bothantlr.ErrorListenerandoqd_compiler_infrastructure.DefaultErrorCollectorAnalogParserErrorListenertoAnalogLexerandAnalogParserinparse_analogfor handling errors that occur in parsing and lexingparse_analog.Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
parse_analognow raises errors if any problems arise during lexing and parsingOther information: