Typescript Strict mode compatibility

[diovannaschell]

Hello, Thanks for all the work with prisma!

I'm trying to update my APIs to use the typescript on Strict mode especially because of the strict null acertions, but enabling this option broke 90% of my code with prisma:

const { _sum: total} = await connection.nfe.aggregate({
            _sum: { value: true },
            where: {
                    deleted: 'false', // This line gives "Type 'string' is not assignable to type 'undefined'.ts(2322)"
                    events: {
                       location: { id: { in: locationsIds } }
                    } // An this "Type '{ location: { id:  { in: number[] } }  }' is not assignable to type 'undefined'.ts(2322)"
                },
                status: 'received',
            },
        });

This is just one example, but almost every where condition in my code now prompts this errors

this is how vsCode shows the deleted property on mouse hover (property) deleted?: string | Prisma.StringNullableFilter | null | undefined

Am I missing something? Typescript Strict mode can be used with prisma?

Thanks in advance

[ovidb]

@diovannaschell have you ended up find a somewhat elegant solution for this? I was thinking of use some type guards but just wondering if you found something

[divmgl]

+1 on this. This is the first time I experience this problem and I'd really like to avoid turning off strict mode. What's going on here? Clearly the type accepts string, so why can't I assign a string? Really strange.

[SwenenzY]

solved?