Feature req: Set session.user.id automatically when using a database adapter

[jasongitmail]

Goals

Automatically make session.user.id available on the session when a database adapter exists in the config, irrespective of whether using a database or jwt session strategy. It should contain the id from the user database table.

Non-Goals

No response

Background

Currently you have to add this manually, like this for a database session:

async session({ session, user }) {
  if (session?.user) {
    // @ts-expect-error Property id does not exist
    session.user.id = user.id;
  }

  return session;
},

but then this also breaks if changing to a session.strategy of jwt.

Proposal

This is so common, it should be default to create a better developer experience, for both sessions stored in the database or jwt, so long as a database adapter exists.

[FunMiles]

I agree. I've written a variant, as I have been switching between database and jwt strategies:

session({ session, token, user }) {
   if (session?.user) {
     // @ts-expect-error Property id does not exist
     session.user.id = user?.id || token?.sub;
   }
   return session
}

[0xMihir]

Also, the session user id outputs an integer, not a string.