Skip to content

Add support for error cause in Neo4jError and Routing errors #960

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jul 5, 2022

Conversation

bigmontz
Copy link
Contributor

@bigmontz bigmontz commented Jul 4, 2022

Root causes of routing issue were suppressed by the routing error message.

This change enables the Neo4jError object use the cause property for giving more context about the error. This
also improves the routing error by making use of the error cause.

Error.cause is a new feature in JS, see which runtime already implemented it:

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/Error

Root causes of routing issue were suppressed by the routing error message.

This change enables the `Neo4jError` object use the `cause` property for giving more context about the error. This
also improves the routing error by making use of the error `cause`.

`Error.cause` is a new feature in JS, see which runtime already implemented it:

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/Error
@bigmontz bigmontz merged commit 551f51c into neo4j:5.0 Jul 5, 2022
@bigmontz bigmontz deleted the 5.0-add-support-for-error-cause branch July 5, 2022 14:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants