Add TokenExtractionError and TokenParsingError types to help distinguishing error source in ErrorHandler #6
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
…ishing error source in ErrorHandler
aldas
force-pushed
the
extra_error_types
branch
from
8d2db81 to
0391aa4
Compare
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.
Add TokenExtractionError and TokenParsingError types to help distinguishing error source in ErrorHandler.
background: one of my own applications does some checking in ErrorHandler and needs to know is error is related to extraction or parsing. Although we just introduced
TokenErrorI think there should be more guaranteed way to differentiate these cases when custom extractors and parserFuncs are being used.