as type error
If no relationships are configured in the model, no type error occurs, but if a relationship model is defined in the model, a type error occurs
async create<T extends Prisma.TokenRecordCreateArgs>(args: T) {
return this.prisma.tokenRecord.create(args) as Promise<Prisma.TokenRecordGetPayload<T>>;
} async create<T extends Prisma.TokenRecordCreateArgs>(args: T) {
return this.prisma.tokenRecord.create(args) as Promise<Prisma.TokenRecordGetPayload<T>>;
}TS2352: Conversion of type
Prisma__TokenRecordClient<{ id: number; subject: 'NONE'; accessToken: string; ip: string; isExpiration: boolean; createdAt: Date; updatedAt: Date; userId: number | null; }, never, DefaultArgs, PrismaClientOptions>
to type
Promise<GetFindResult<$TokenRecordPayload<DefaultArgs>, T, {}>>
may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to unknown first.
Types of property then are incompatible.
Type '<TResult1 = { id: number; subject: "NONE"; accessToken: string; ip: string; isExpiration: boolean; createdAt: Date; updatedAt: Date; userId: number | null; }, TResult2 = never>(onfulfilled?: ((value: { id: number; subject: "NONE"; ... 5 more ...; userId: number | null; }) => TResult1 | PromiseLike<...>) | null | und...' is not comparable to type '<TResult1 = GetFindResult<$TokenRecordPayload<DefaultArgs>, T, {}>, TResult2 = never>(onfulfilled?: ((value: GetFindResult<$TokenRecordPayload<DefaultArgs>, T, {}>) => TResult1 | PromiseLike<...>) | null | undefined, onrejected?: ((reason: any) => TResult2 | PromiseLike<...>) | ... 1 more ... | undefined) => Promise...'.
Types of parameters onfulfilled and onfulfilled are incompatible.
Types of parameters value and value are incompatible.
Type
{ id: number; subject: 'NONE'; accessToken: string; ip: string; isExpiration: boolean; createdAt: Date; updatedAt: Date; userId: number | null; }
is not comparable to type
GetFindResult<$TokenRecordPayload<DefaultArgs>, T, {}>TS2352: Conversion of type
Prisma__TokenRecordClient<{ id: number; subject: 'NONE'; accessToken: string; ip: string; isExpiration: boolean; createdAt: Date; updatedAt: Date; userId: number | null; }, never, DefaultArgs, PrismaClientOptions>
to type
Promise<GetFindResult<$TokenRecordPayload<DefaultArgs>, T, {}>>
may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to unknown first.
Types of property then are incompatible.
Type '<TResult1 = { id: number; subject: "NONE"; accessToken: string; ip: string; isExpiration: boolean; createdAt: Date; updatedAt: Date; userId: number | null; }, TResult2 = never>(onfulfilled?: ((value: { id: number; subject: "NONE"; ... 5 more ...; userId: number | null; }) => TResult1 | PromiseLike<...>) | null | und...' is not comparable to type '<TResult1 = GetFindResult<$TokenRecordPayload<DefaultArgs>, T, {}>, TResult2 = never>(onfulfilled?: ((value: GetFindResult<$TokenRecordPayload<DefaultArgs>, T, {}>) => TResult1 | PromiseLike<...>) | null | undefined, onrejected?: ((reason: any) => TResult2 | PromiseLike<...>) | ... 1 more ... | undefined) => Promise...'.
Types of parameters onfulfilled and onfulfilled are incompatible.
Types of parameters value and value are incompatible.
Type
{ id: number; subject: 'NONE'; accessToken: string; ip: string; isExpiration: boolean; createdAt: Date; updatedAt: Date; userId: number | null; }
is not comparable to type
GetFindResult<$TokenRecordPayload<DefaultArgs>, T, {}>