Render ProgrammingError, CompilationError and ParserError alway user-friendly #266
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
…friendly Change `render_exception()` so that it does not show a stack trace if no AST node information is provided to CompilationError. Also, do not print a stack trace for `ProgrammingError`s, as these are also errors committed by the user and therefore should have a nice error message without a stack trace.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 should fix #261.
Change
render_exception()so that it does not show a stack trace if no AST node information is provided to CompilationError.Also, do not print a stack trace for
ProgrammingErrors, as these are also errors committed by the user and therefore should have a nice error message without a stack trace.