[SLING-10540] Selector-driven prepared GraphQL queries

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: GraphQL Core 0.0.10
• Component/s: GraphQL
• Assignee: Bertrand Delacretaz
• Reporter: Bertrand Delacretaz
• Created: 24/Jun/21 08:37
• Updated: 24/Jun/21 08:37

Description

I'd like to implement selector driven prepared queries, here's a rough spec:

• Any Sling resource can be a GraphQL endpoint (already implemented).
• If a GET request includes selectors, they can point to a prepared GraphQL query.
• A PreparedQueryProvider service is used to store and retrieve prepared queries.
• A GraphQL Mutation (to the same URL) can be used to store prepared queries depending on the user authorizations.
• When executing a prepared query, the HTTP request parameters are provided as GraphQL query variables

The goal is similar to the /persisted API that we already support, but "in-place" without having to address a different resource to run the query, and using a Mutation to store it, for consistency . It should be possible to disable both the /persisted mechanism and this new variant by configuration, as in most cases we probably don't want to have both active.