Hi there.
I seem to be having an issue since trying to move from a single APOLLO_OPTIONS provider to multiple named APOLLO_NAMED_OPTIONS providers, now that I need to support another HTTP/WSS endpoint.
My initial setup used a split link for HTTPS and WSS to subscribe to a SubGraph:
updateQuery error: Error: invalid query: no fields for type `Query`
at new ApolloError (index.js:29:28)
at QueryManager.js:494:27
at Object.next (module.js:305:21)
at notifySubscription (module.js:132:18)
at onNotify (module.js:176:3)
at SubscriptionObserver.next (module.js:225:5)
at iteration.js:4:68
at Array.forEach (<anonymous>)
at iterateObserversSafely (iteration.js:4:25)
at Object.next (Concast.js:25:43)
I am using "apollo-angular": "^4.1.1" and "@apollo/client": "^3.7.1"
Is there anything I need to change in the construction on my initial query and subscription?
This was also happening in 4.1.0, though I had to use the name 'default' to get the default client. Then I saw the recent fix pushed for that.
Hi there. I seem to be having an issue since trying to move from a single
APOLLO_OPTIONS
provider to multiple namedAPOLLO_NAMED_OPTIONS
providers, now that I need to support another HTTP/WSS endpoint.My initial setup used a split link for HTTPS and WSS to subscribe to a SubGraph:
In app.module.ts:
All this works fine. In my subgraph service, my query and subscription are all returned and updated ok, using:
But when I attempt to use a named provider (called 'two', but currently set to use the same uris), set up in app.module.ts using:
and then, in my service, I use the named client 'two' (or using the default):
.. I get an error in updateQuery:
I am using
"apollo-angular": "^4.1.1"
and"@apollo/client": "^3.7.1"
Is there anything I need to change in the construction on my initial query and subscription?
This was also happening in
4.1.0
, though I had touse
the name'default'
to get the default client. Then I saw the recent fix pushed for that.Any ideas?
Many thanks!