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
Alteration (enhancement/optimization) of existing feature(s)
New behavior
Description
It would be useful for people to be able to load schemas on the fly (lazily at runtime) instead of binding them in a view. This could be used for dynamic graphql servers, when you need to serve a different schema per user context.
express-graphql does this by allowing the schema to be resolved lazily.
Similar to this example: graphql/express-graphql#791
Note that in this case the options: Options is either an Object or a promise returning an object.
Apollo does not offer this by default, only by using a dangerous hack (which unfortunately is used in production in a few places that I've seen):
Feature Request Type
Description
It would be useful for people to be able to load schemas on the fly (lazily at runtime) instead of binding them in a view. This could be used for dynamic graphql servers, when you need to serve a different schema per user context.
express-graphql
does this by allowing the schema to be resolved lazily.Similar to this example:
graphql/express-graphql#791
Note that in this case the
options: Options
is either an Object or a promise returning an object.Apollo does not offer this by default, only by using a dangerous hack (which unfortunately is used in production in a few places that I've seen):
apollographql/apollo-server#2010 (comment)
Upvote & Fund
The text was updated successfully, but these errors were encountered: