[RFC] Persisted Operations about graphql-gateway-specifications HOT 4 OPEN

Hey,

Wanted to jump in here to say that maybe we can formalise the request format with the rfc not sure if y'all have opinions here but omitting query is currently not allowed when strictly following the http spec. Specifying operationName should be allowed so folks are allowed to specify an exact operation from a hash imho.

from graphql-gateway-specifications.

As for the protocol, I would prefer a non-/graphql endpoint protocol extension -and rather a /<prefix>/<documentHash>/<optionalExecutionalOperationName> format. Where depending on whether it is a mutation or query, either a POST request or GET request must be used. We would also need to figure out how to support this with The GraphQL over WS and GraphQL over SSE protocols.

from graphql-gateway-specifications.

The store could also be external, e.g. an S3 bucket as in a setup with many GraphQL clienrs you rarely can embed all all client operations within the gateway at deployment time. for several reasons: many different client versions (where every client has different GraphQL operations that beed to be supported) or logistical issues (client code being in many different repositories that you may or may not control).

from graphql-gateway-specifications.

One thing that is often overlooked isbthat a GraphQL document can contain multiple executable operation definintions, where the actual operation being executed is determined via the operationName parameter. I think the persisted document protocol should still allow that to be as spec compatible as possible.

from graphql-gateway-specifications.