Skip to content
This repository has been archived by the owner on Jul 17, 2022. It is now read-only.

fix(neo4j): update user bugfix #352

Merged

Conversation

EarthlingDavey
Copy link
Contributor

Reasoning 💡

Using the neo4j adapter, I noticed that if I sign in with Facebook, then, with email - it fails.

The reason being that updateUser returned an object like { 'properties(u): { id: '123', name: 'abc' } },}`

This PR fixes that by returning a user object fromupdateUser

In addition I have used shorter notation u{.*} instead of properties(u) throughout all neo4j statements.

And, to catch this bug in future, I have made an edit to basic-tests.js for your consideration.

Checklist 🧢

- [ ] Documentation

  • Tests
  • Ready to be merged

Affected issues 🎟

Dupe of PR #348 except for main branch

@github-actions github-actions bot added the neo4j @next-auth/neo4j-adapter label Dec 22, 2021
@balazsorban44 balazsorban44 merged commit 8c4ddbd into nextauthjs:main Dec 23, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
neo4j @next-auth/neo4j-adapter
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants