Michael Staib
Michael Staib
is it in your repo ... for inputs?
OK ... I will have a look at it
This one is fixed with 15.1.6
It's a bit too late for 14 to add this ... but I will add it to the 14.1 backlog
Yes ... a type interceptor is also how we will implement it in the core.
@rohinz good point ... often simple type extensions are the simplest way to do these things :)
This is now implemented
https://github.com/ChilliCream/graphql-platform/releases/tag/14.0.0-p.163
In this case its kind of correct. Since we cannot fully inspect what the impact is of custom expressions the field will be executed on the standard path which is...
We could however add another configuration method that allows mapping states ... like ``` builder.Services.AddGraphQLServer().AddQueryType().MapGlobalState(key); ``` which we know is pure and then weight it as pure.