-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for defining custom links #563
Comments
hi @bmulholland , |
Thanks for the idea, Ashot :). On my end, I ended up just dropping Nuxt Apollo and configuring it directly myself. That was easy because we don't use SSR. |
Got you, as long as not SSR, no need to use nuxt apollo, and I am sure that your solution is the best. |
Hey Brendan -- are you then using https://github.com/Akryum/vue-cli-plugin-apollo direct? I am in the same boat but ended up writing a plugin which works around this limitation but still using the module (to some extent). It works but I have the feeling that it's not needed as I have deviated far enough from the "simple" use case of the nuxt module. |
I'm on Vue 3/Vite now, which drops Vue CLI support, so it's https://github.com/vuejs/apollo directly. |
Your use case
We're upgrading to Nuxt 3 from Nuxt 2. When upgrading Nuxt Apollo, I see there's no longer any way to pass in our custom ApolloLink. We already had this working using a complex link chain, which supports both file uploads (ref: #553) but also has a custom link for websockets via Rails Action Cable.
Removing this option is backwards-incompatible. We'll have to do the same as others and write our own plugin, I guess. Then we'll have to maintain that ourselves, too, which I prefer not to do.
The solution you'd like
Allow overriding links, like used to be available.
Possible alternatives
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: