fix(dgraph): id generation overlap

[korzhanov]

☕️ Reasoning

Dgraph will generate the ID by itself. In Dgraph, every node has a unique 64-bit identifier that you can expose in GraphQL using the ID type. An ID is auto-generated, immutable and never reused. Each type can have at most one ID field.

The ID type works great when you need to use an identifier on nodes and don’t need to set that identifier externally
DGraph type docs

Since next-auth.js or auth.js creates a new user id, this causes an error and does not save the entry to dgraph

🧢 Checklist

• Documentation
• Tests
• Ready to be merged

🎫 Affected issues

📌 Resources

• Security guidelines
• Contributing guidelines
• Code of conduct
• Contributing to Open Source

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
auth-docs	❌ Failed (Inspect)			Apr 24, 2024 9:24pm

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
next-auth-docs	⬜️ Ignored (Inspect)	Visit Preview		Apr 24, 2024 9:24pm

[ndom91]

Just curious why the current tests pass and why this isn't necessary for createSession or createVerificationToken, for example, then? 🤔

[korzhanov]

@ndom91 Sorry, I didn't see your comment in this thread without mention.

Just curious why the current tests pass and why this isn't necessary for createSession or createVerificationToken, for example, then? 🤔

The test uses a predefined id value id: () => "0x0a0a00a00" that falls under the DGraph requirements.

next-auth/packages/adapter-dgraph/test/index.test.ts

Lines 22 to 43 in 770112c

	runBasicTests({
	adapter: DgraphAdapter(params),
	db: {
	id: () => "0x0a0a00a00",
	async disconnect() {
	await c.run(/* GraphQL */ `
	mutation {
	deleteUser(filter: {}) {
	numUids
	}
	deleteVerificationToken(filter: {}) {
	numUids
	}
	deleteSession(filter: {}) {
	numUids
	}
	deleteAccount(filter: {}) {
	numUids
	}
	}
	`)
	},

And in reality, the random UUID is invalid, it doesn't match the DGraph UID conditions.

Situation similar to the FaunaDB adapter

next-auth/packages/adapter-fauna/test/index.test.ts

Lines 17 to 26 in 770112c

	runBasicTests({
	adapter: FaunaAdapter(client),
	db: {
	// UUID is not a valid ID in Fauna (see https://docs.fauna.com/fauna/current/reference/fql_reference/types#id)
	id: () => String(Math.floor(Math.random() * 10 ** 18)),
	user: async (id) => {
	const response = await client.query<FaunaUser>(fql`User.byId(${id})`)
	if (response.data instanceof NullDocument) return null
	return format.from(response.data)
	},

And I think maybe createSession and createVerificationToken don't use external generated ids, only internal ones