Fabrizio Ruggeri
Fabrizio Ruggeri
I have the same error for any model though, so I don't think it's related to this in particular
I see. Any workaround we can put in place? I guess I can omit 'cursor' from my type, but this is not a global solution. Maybe the type of cursor...
Today I stumble on a related issue. I have two entities like this ``` Project { id: string outputs: [Output] } ``` I fetch the project and ask for the...
I will open an issue soon with more details and hopefully a reproduction, but not in the next few days because I changed focus at the moment. Thanks. Meanwhile reading...
I see,but in this case how can it invalidate the list of entity B that I fetch when I get entity A? If I create a new entity B I...
Also,manually calling `cache.invalidate('Output')` is exactly what stellate is doing. I think the rationale behind it is that you're not always in control of the mutations sent to your system
This would be great actually. So at the level of mutation definition, e.g. OutputCreate we can declarative state "this mutation invalidates Output"
Any update about this? At the moment it's not possible to use plover on macos
I have the same problem. Did you reach any conclusion maybe?
Actually I did. It's important to not specify a `name` property in the security scheme