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
Is your feature request related to a problem? Please describe.
After #901 SSR bails out when any vue-apollo query fails.
However one could alternatively still want to still have the page rendered even if one of the requests failed. If it's some network issue, the query can automatically retry in the client.
With direct access to serverPrefetch one had the option of doing that by resolving the Promise if it fails and handling the error, but that's not possible with component queries.
Describe the solution you'd like
An option on global level and/or on request level to decide whether that particular call is allowed to fail. For example:
constapolloProvider=newVueApollo({defaultProvider: apolloClient,rejectSsrOnQueryError: false// or any better name})
Hi there. We've been bitten by this omission in our app and were wondering if there was any way we could help get it done.
Just to give an idea of what's happening for us: our system is designed in such a way that there are multiple individual modules on a single page that have individual queries. The modules are meant to handle their own errors and show a local failure instead of the entire page failing to load. As it stands, the only way for us to fix this is to only run graphql queries on the client (defeating most of the benefits of doing SSR).
Is your feature request related to a problem? Please describe.
After #901 SSR bails out when any
vue-apollo
query fails.However one could alternatively still want to still have the page rendered even if one of the requests failed. If it's some network issue, the query can automatically retry in the client.
With direct access to
serverPrefetch
one had the option of doing that by resolving the Promise if it fails and handling the error, but that's not possible with component queries.Describe the solution you'd like
An option on global level and/or on request level to decide whether that particular call is allowed to fail. For example:
Or in smart query level:
Describe alternatives you've considered
Naming it
bailRenderingOnError
.The text was updated successfully, but these errors were encountered: