Skip to content
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

Make sure aliases are checked against connectOrCreate where input #1142

Merged

Conversation

darrellwarde
Copy link
Contributor

Description

When generating the initial MERGE in a connectOrCreate, the input where object was not being checked against aliases for database properties. This adds that check.

Issue

Closes #1131.

Checklist

The following requirements should have been met (depending on the changes in the branch):

  • Documentation has been updated
  • TCK tests have been updated
  • Integration tests have been updated
  • Example applications have been updated
  • New files have copyright header
  • CLA (https://neo4j.com/developer/cla/) has been signed

@darrellwarde darrellwarde requested a review from angrykoala March 16, 2022 12:47
@darrellwarde darrellwarde linked an issue Mar 16, 2022 that may be closed by this pull request
@darrellwarde
Copy link
Contributor Author

I don't know what to do about the non-null assertions here - TypeScript not detecting that the variable is not undefined despite having an explicit check.

@angrykoala angrykoala merged commit 3f047cc into neo4j:master Mar 17, 2022
@darrellwarde darrellwarde deleted the fix/1131-alias-bug-connect-or-create branch May 9, 2022 16:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Issues with aliases on connectOrCreate v2
3 participants