Wrong inferred type

Hi,
I don't know why, but inferSession still has the ID as a string, same for the user, even though I set:

database: {
    useNumberId: true,
    generateId: false
}

database: {
    useNumberId: true,
    generateId: false
}

database: {
    useNumberId: true,
    generateId: false
}

database: {
    useNumberId: true,
    generateId: false
}

Vvpjm Hi, I don't know why, but inferSession still has the ID as a string, same for th...

Ping•5/25/25, 4:43 PM

Hello, this is by design. Our adapter system will translate the data accordingly so nothing to worry about.

vpjmOP•5/25/25, 5:04 PM

So I need to cast the type to ensure proper typing ?
Have you planned a way to cast the type associated with the user, session, etc., using generics for example? Or do we still have to work around it by manually tweaking the return type?

vpjmOP•5/25/25, 5:04 PM

Thanks for your answer !!

Vvpjm So I need to cast the type to ensure proper typing ? Have you planned a way to ...

Ping•5/25/25, 6:35 PM

What I mean is the

id

id

will still be a string, in the DB it may be a number, but it will be converted to a string automatically.

borism•6/16/25, 1:21 PM

Hey hey, just chiming in here.

Are there any thoughts on changing this? I'd expect the $Infer.Session.user.id type to be int not string after setting useNumberIduseNumberId. Same for the response schema of endpoints like /sign-up/email

Bborism Hey hey, just chiming in here. Are there any thoughts on changing this? I'd ex...

Ping•6/16/25, 4:58 PM

It's very unlikely this will change. Everything built in and around better-auth runs with the expectation of

id

id

being a string. If we converted it to a number lots of plugins and libraries that work with Better Auth will have issues.

Wrong inferred type

Similar Threads

Similar Threads

Similar Threads