Upon using this generator I've ran into an issue where the not condition was mandatory for some of the typed filters.
I think this was a mistake, so I've pushed a PR where this is no longer the case, alongside some tests.
Before this fix when making a WHERE IN, we'd be forced to make a WHERE NOT as well by ts.
Example before fix:
prismaClient.someModel.findFirst({
where: {
someColumn: {
in: [ ...listOfValues ],
not: 'I have to include a not condition too otherwise ts complains :( how sad'
},
},
});
Upon using this generator I've ran into an issue where the
not
condition was mandatory for some of the typed filters.I think this was a mistake, so I've pushed a PR where this is no longer the case, alongside some tests.
Before this fix when making a
WHERE IN
, we'd be forced to make aWHERE NOT
as well by ts.Example before fix:
Now