Implement new error handling pattern for scripting#30
Merged
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
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.
New Error Type
Errors now can be described through the following syntax from within Rust:
Additionally,
fshas been migrated to specifically use these errors, and existing errors should continue to function in a second-class manor until manual work is done to port them over.Use from Rhai
The following getters were created to better take advantage of new context-rich errors:
.class
Returns the class that this error belongs to:
.name
Returns a deterministic string that can be matched upon to identify error type:
.msg
Returns message containing human readable description of the error:
.pretty
Returns a pretty print of the error: