You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am migrating from next-auth-2 to next-auth-3, then immediately to next-auth-4.
Base on the documentation here, a few MongoDB fields must be migrated. However, my database structure is not the same as what is expected in the documentation!
Here is an example of an account document in my db:
Is is normal that my database was using camel case instead of snake case?
can I configure next-auth/mongodb-adapter to use camel case? So that I only have to migrate providerId => provider and accessTokenExpires => expiresAt?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am migrating from next-auth-2 to next-auth-3, then immediately to next-auth-4.
Base on the documentation here, a few MongoDB fields must be migrated. However, my database structure is not the same as what is expected in the documentation!
Here is an example of an account document in my db:
All the fields are in camel case. The migration documentation expects snake case.
The new fields uses a mix a snake and camel case:
providerId => provider
andaccessTokenExpires => expiresAt
?Beta Was this translation helpful? Give feedback.
All reactions