Shane Krueger

> So "persisted documents" is effectively a middleware in front of a GraphQL service - the incoming request is decoded as GraphQLPersisitedDocumentRequest, converted to GraphQLRequest and then fed onto the...

I agree that if persisted queries are part of the official spec, then it is better that they have their own property within `GraphQLRequest` rather than utilizing `extensions`, saving `extensions`...

_Originally posted by @benjie in https://github.com/graphql/graphql-over-http/issues/260#issuecomment-1744419339_ : > One of the big outcomes for me during GraphQLConf is that almost all of the attendees should have been using persisted operations...

> I'm in no hurry to specify APQ in this, not least because Apollo's APQ spec already exists and works fine Isn't this equally true for white-listed persisted query support?...

Yes... and no. GraphQL.NET 7 adds the `User` property to `IResolveFieldContext` in order to provide a dedicated field in which to hold the identity and claims in the form of...

@tlil It is likely possible without too much difficulty to support `GraphQLAttribute`-based attributes for metadata. During construction of the graph type or field definition, these methods would need to be...

You want the returned products filtered by both the product name and the seller name?

If I understand your question correctly, I would suggest moving the additional filter up to the parent node. So the request looks like this: ```gql { Product( filter: { ProductName:...

See also: - #2164

The authorization validation rule included with GraphQL.Server supports AllowAnonymous, effectively white listing a specific field within a graph type. There are other differences so be sure to read the documentation...