You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 20, 2023. It is now read-only.
Allow clients that send queries to use predefined fragments on the server side.
The goal:
Shorten the query for every client by avoiding to repeat the fragment declaration.
Allow the client to have dynamic fragments that are updated server side. For example, if a field was added to the schema server side, the fragment will update accordingly.
acao, Ariel-Dayan, SMontero90, jeanbmar and snys98
to follow conventions elsewhere, we might accomplish this via graphql-config where folks are already using similar capability for IDE tooling? but it should also be possible without graphql-config
Activity
feat(server fragments): server predefined fragments
acao commentedon Dec 9, 2019
to follow conventions elsewhere, we might accomplish this via graphql-config where folks are already using similar capability for IDE tooling? but it should also be possible without graphql-config
acao commentedon Dec 9, 2019
@Urigo what do you think about graphql-config plus express-graphql? I know we've been mostly focused on this for dev tooling