Skip to content

This change fixes an issue where properties got unset for when updating a node #117

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

Conversation

Andy2003
Copy link
Collaborator

Now we always use SET x += {} to update properties.

fixes #105

…nset for when updating a node.

Now we always use `SET x += {}` to update properties.
@Andy2003 Andy2003 requested a review from jexp August 28, 2020 09:47
Copy link
Contributor

@jexp jexp left a comment

Choose a reason for hiding this comment

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

Looks good, thanks a lot!

@jexp jexp merged commit b4867a5 into neo4j-graphql:master Aug 30, 2020
@Andy2003 Andy2003 deleted the bugfix/GH-105-use-porperty-update-on-merge branch August 31, 2020 07:20
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.

Don't use assignment for MERGE/Update
2 participants