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
I am implementing my own link (not based on http). If I exclude apollo-link-http from packages (to save some space) the apollo service will crash because unable to load apollo-link-http. Would you accept a PR to have a BaseApolloService without apollo-link-http (and maybe without cache) from which ApolloService will inherit and from which users can inherit in advanced cases?
The text was updated successfully, but these errors were encountered:
Yes, the design you describe makes a lot of sense. Ideally we should support the most common use case out-of-the-box with little/no required config, but also make it possible to serve more advanced use cases like yours.
Regarding the name, this is somewhat unconventional but what do you think about ApolloBaseService instead of BaseApolloService? I like it because it keeps the Apollo prefix.
I am implementing my own link (not based on http). If I exclude
apollo-link-http
from packages (to save some space) the apollo service will crash because unable to loadapollo-link-http
. Would you accept a PR to have aBaseApolloService
withoutapollo-link-http
(and maybe without cache) from whichApolloService
will inherit and from which users can inherit in advanced cases?The text was updated successfully, but these errors were encountered: