did you use an adapter?

what is your session strategy?

can you send full auth option

code block is more preferable

use the session() callback to handle new users

events are meant to be side effects and not for db calls

although

ok, i'll take the advice

i thought you already use prisma adapter

you don't need to update again unless you want to change it even after the update?

I use t3 stack. It provides a boilerplate for prisma where user have fields like name, email. I added another unique field "username". When user signs in via github or discord i want them to be redirected to /auth/new-user page where they should provide a username or else it will be set to default value "user[id"]

Or is there a better way to implement this?

ahh i see

i have no clue on how to add custom new user page natively in nextauth

but i have some idea

such as returning the session with isInitialized flag put in your session object

if its not initialized, then redirect to new user

if its initialized then continue as usual

so after finishing the new-user page you can useSession().update() to update session to mark isInitialized to true

thanks, i'll try that

I should extend the session interface and add isInitialized to prisma schema, right?

oh yeah

that too

So then i should make the username field optional, because user is created after they signed in via provider and username will be set later, right?

whaaa

your username should be in the register page, not the new-user page

i thought ure talking about the introductory page after a new user had signed in

oops

ok my bad

is there a github repo with custom sign up page for providers? I couldn't find one

Do you know how to implement it? After they signed in via provider, make them provide additional data (username)?