-
Notifications
You must be signed in to change notification settings - Fork 742
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Client extensions: $allOperations limitations #5057
Comments
Do you know if there has been any progress on this issue? The code works just fine but there are build errors. I don't want to enable ignoreBuildError in next.config.js. Also, this error is not ignorable using // eslint-disable-next-line $allOperations extensions are critical for our current multitenant solution. Would love to find a solution to this. If anyone has found work or fix around, I'd love to hear. |
Please open an issue in https://github.com/prisma/prisma. Thanks. |
This issue is already articulated very well on this ticket from @ul8. I am happy to create a new ticket, but it be a duplicate this one. If an issue is required to get this fixed. I will submit one. |
Having the same issue, would appreciate a fix. That is crucial for multi tenancy development. |
Bug description
prisma.$extends typescript validation fails when trying to modify all operations in a specific model
I get a type error on
args.where
How to reproduce
Code that works fine:
When I change it to this it starts showing the above error
Expected behavior
From reading the documentation, I would expect not to see any error here.
If this is expected behavior, the documentation could probably be improved.
To be clear, it does work, just the type errors are the problem.
Prisma information
Environment & setup
Prisma Version
The text was updated successfully, but these errors were encountered: