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
How to add use of apollo-error-link with version 4 ?
In version 3 i was having this:
const errorLink = onError(({ graphQLErrors, networkError }) => {
if (networkError) {
ctx.app.$messages.showErrorMessage(networkError.message)
}
if (graphQLErrors) {
graphQLErrors.map(({ message }) =>
ctx.app.$messages.showErrorMessage(message)
)
}
})
const link = middlewareLink.concat(errorLink).concat(httpLink)
return {
link,
cache: new InMemoryCache()
}
I dont see how can i add onError handler for version 4 of plugin.
PS asked on cmty as question ( https://cmty.app/nuxt/apollo-module/issues/c93 ) but it doesnt import into github and i didnt see any replied to any questions that is solely on cmty without github, so it made me think that its not monitored at all..
This question is available on Nuxt community (#c97)
The text was updated successfully, but these errors were encountered:
This issue as been imported as question since it does not respect apollo-module issue template. Only bug reports and feature requests stays open to reduce maintainers workload.
If your issue is not a question, please mention the repo admin or moderator to change its type and it will be re-opened automatically.
Your question is available at https://cmty.app/nuxt/apollo-module/issues/c97.
@aldarund I will close the issue here. Please open a ticket on vue-cli-plugin-apollo as soon the option is available there I will provide its functionality in this package as well
How to add use of apollo-error-link with version 4 ?
In version 3 i was having this:
I dont see how can i add onError handler for version 4 of plugin.
PS asked on cmty as question ( https://cmty.app/nuxt/apollo-module/issues/c93 ) but it doesnt import into github and i didnt see any replied to any questions that is solely on cmty without github, so it made me think that its not monitored at all..
The text was updated successfully, but these errors were encountered: