Hi everybody. I once asked a similar question, but now I have to return to it, since there are huge problems on our project because of it. Tell me, is there any sane way (except for making own fork from the prisma) to disable validation for extra fields in the parameters in the mutation methods? Due to this stupid check, we are forced to write thousands of additional lines of code in each method working with the prism, in order to transfer all fields from some object to a new object in it, in which only those fields that the prisma will process are guaranteed ... Since if an object with extra fields arrives during runtime, there will be a runtime error

@Mykyta Machekhin 👋 Have you created a feature request for this? Because I don’t think there’s any way to allow extra fields directly.