feat(#3743): Add Error Location for Custom Errors #3766
Merged
Conversation
This file contains 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
…e and write our excpectations
|
@maxonfjvipon Could you review these changes, please? |
maxonfjvipon
approved these changes
Dec 26, 2024
|
@yegor256 Can you take a look, please? |
|
@volodya-lombrozo Thanks for the contribution! You've earned +6 points for this: +4 as a basis; +6 for the 128 hits-of-code that you wrote; -4 for very few (2) comments. Please, keep them coming. Your running balance is -4. |
|
@maxonfjvipon Thanks for the review! You've earned +4 points for this: +4 as a basis; -10 for very few (2) comments; +10 to give you at least something. Your running balance is +24. |
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.
In this PR I added location and helpful information to custom parsing errors.
Was:
Become:
Closes: #3743.