-
Notifications
You must be signed in to change notification settings - Fork 39
SURF-537 Update documentation for type mismatch errors #450
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
base: dev
Are you sure you want to change the base?
Conversation
renetapopova
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @neo-harshg. Which version is this applicable to?
gem-neo4j
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great :)
c15f909 to
10b47ba
Compare
renetapopova
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @neo-harshg. I've pushed some editorial changes. The error looks good, but what about these notifications https://github.com/neo4j/docs-status-codes/blob/dev/modules/ROOT/pages/notifications/all-notifications.adoc?
See Example 27. Setting properties using a node, and Example 28. Setting properties using a relationship
Do we need to update them somehow? I am confused now about what this query will throw - a notification or an error.
|
This PR includes documentation updates Updated pages: |
https://linear.app/neo4j/issue/SURF-537/better-error-message-for-queries-like-match-a-b-set-a-=-b