Is it normal prisma fluent api consider non-nullable relations as nullable ?

No it’s a bug. I see you have opened an issue and there’s also a related issue for the same here.

I was wondering if it's normal because

findUnique

can actually return null. So it may be logic that relation query return null also. But thanks to confirm it's a bug ^^

It can but only if

rejectOnNotFound

is set to false. Otherwise it can return

null

.

My only concern is to make this code working 😁

Only way for now would be to either remove the

nonNull

or not use the fluent API and stick to

include

.

thx Ryan 😉