Nexus error chain workaround #944
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
bergundy
approved these changes
Jul 7, 2025
| # but it should be "runtime-error-message" | ||
| # "message": "runtime-error-message", | ||
| "message": "handler-error-message", | ||
| "type": "nexusrpc._common.HandlerError", |
There was a problem hiding this comment.
I think you can drop the type here.
dandavison
added a commit
that referenced
this pull request
Jul 8, 2025
* Always move first error message to top-level * Inject ApplicationError
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Inject an additional error into the cause chain to work around the fact that
HandlerErroris an independent exception with its own error message and stack trace (unlike Go and Java).