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
In our app, we have a fair number of commonly used fragments (especially for queries triggered via non-UI code). It'd be pretty handy to register fragments globally with an apollo-client instance to cut down on verbosity when querying
Maybe as a fragments argument when constructing the client?
The text was updated successfully, but these errors were encountered:
We thought about this when designing the createFragment concept. At the time, we came to the conclusion that handling global state like this might actually be somewhat complicated to reason about and we went with a more local approach.
However, from the discussion in #480, it is evident that we will end up implementing this in some capacity since we want to be able to reference fragments by names only rather than by the references returned by createFragment.
In our app, we have a fair number of commonly used fragments (especially for queries triggered via non-UI code). It'd be pretty handy to register fragments globally with an apollo-client instance to cut down on verbosity when querying
Maybe as a
fragments
argument when constructing the client?The text was updated successfully, but these errors were encountered: