Enh(#843): Allow signup flow return data when preventLoginFlow is true

[iamKiNG-Fr]

🔗 Linked issue

#843

❓ Type of change

• 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Added functionality to allow user receive response from server after signup, when preventLoginFlow is true.

📝 Checklist

• I have linked an issue or discussion.
• I have added tests (if possible).
• I have updated the documentation accordingly.

[pkg-pr-new]

Open in Stackblitz

pnpm add https://pkg.pr.new/@sidebase/nuxt-auth@903

commit: 98e33a9

[phoenix-ru]

Could you please update your handler to be closer to a demo implementation introduced in #901?

https://github.com/sidebase/nuxt-auth/blob/main/playground-local/server/api/auth/login.post.ts

I think you either can:

1. return a "user" object and no access token (we are doing preventLoginFlow, right?) in

   nuxt-auth/playground-local/server/api/auth/login.post.ts

   Lines 61 to 65 in 5276a97

   	const user = {
   	username,
   	picture: 'https://github.com/nuxt.png',
   	name: `User ${username}`
   	}

   ;
2. or do both "user" object and access tokens as in signIn handler so that reference is usable by others as inspiration and also by tests.
   

   nuxt-auth/playground-local/server/api/auth/login.post.ts

   Lines 67 to 90 in 5276a97

   	const tokenData: JwtPayload = { ...user, scope: ['test', 'user'] }
   	const accessToken = sign(tokenData, SECRET, {
   	expiresIn: ACCESS_TOKEN_TTL
   	})
   	const refreshToken = sign(tokenData, SECRET, {
   	// 1 day
   	expiresIn: 60 * 60 * 24
   	})
   	// Naive implementation - please implement properly yourself!
   	const userTokens: TokensByUser = tokensByUser.get(username) ?? {
   	access: new Map(),
   	refresh: new Map()
   	}
   	userTokens.access.set(accessToken, refreshToken)
   	userTokens.refresh.set(refreshToken, accessToken)
   	tokensByUser.set(username, userTokens)
   	return {
   	token: {
   	accessToken,
   	refreshToken
   	}
   	}

It is fine for me if you don't want to implement option 2, I can take it over.

[iamKiNG-Fr]

I think you should take over to implement option 2.

I'm not so confident in working with tokens, i would like to learn by seeing your implementation.
I don't mind trying to implement it though if you don't mind, although it might take some trial and error on on my part.