has anyone ever had a situation where they have a service returning some object from prisma that works fine, then you try to mutate the object (for filtering before sending to the client) and GraphQL somehow magically decides that is not what you wanted to do and continues sending the same response?
Oddly, if I create a completely new value, GraphQL returns that and crashes, if I use the prisma query result, I can make mutations to it and it will JSON.stringify as the modified value before going into the magic box that is GraphQL, to be turned into the original result from prisma, where none of the filtering has been applied