Skip to content

Conversation

bigmontz
Copy link
Contributor

There was two different errors durint the unknown request error treatment.

First, the stringfy function was not define in the LocalController scope. It get solve by extract this function to it own file and import it in the local.js.

Second, the backend was capturing the error in the request event and calling writeBackendError with the error object instead of the message.

There was two different errors durint the unknown request error treatment.

First, the stringfy function was not define in the LocalController scope. It get solve by extract this function to it own file and import it in the local.js.

Second, the backend was capturing the error in the `request` event and calling `writeBackendError` with the error object instead of the message.
@bigmontz bigmontz requested a review from robsdedude January 20, 2022 13:45
Copy link
Member

@robsdedude robsdedude left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧵

@bigmontz bigmontz merged commit 213950c into neo4j:5.0 Jan 20, 2022
@bigmontz bigmontz deleted the 5.0-fix-stringify-call branch January 20, 2022 16:01
bigmontz added a commit to bigmontz/neo4j-javascript-driver that referenced this pull request Feb 4, 2022
There was two different errors during the unknown request error treatment.

First, the stringify function was not define in the LocalController scope. It get solve by extract this function to it own file and import it in the local.js.

Second, the backend was capturing the error in the `request` event and calling `writeBackendError` with the error object instead of the message.
bigmontz added a commit that referenced this pull request Feb 4, 2022
There was two different errors during the unknown request error treatment.

First, the stringify function was not define in the LocalController scope. It get solve by extract this function to it own file and import it in the local.js.

Second, the backend was capturing the error in the `request` event and calling `writeBackendError` with the error object instead of the message.
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