Drew Baker

Just ran into this on version `4.0.0-rc19`

I ran into a an issue just now where I had a `pollInterval` setup on the parent of a `nuxt-child`, and when the route changes to the nuxt-child, the next...

Whats interesting is if I do something like this: ``` "$route.params.id"(newVal, oldVal) { if (oldVal) { setTimeout(() => { this.$apollo.queries.tickets.refetch() }, 1000) } } ``` This runs when you come...

My error was due to a GQL query missing an ID. ``` project { id # Without this, it caused the above error timezone } ``` I figured it out...

Yes totally, but shouldn't smart queries default to use fetch() now?

Well the advantage of `fecth()` is that it doesn't have to be at the page level to be SSR's. It can be on a deep component and still be SSR'd....

I'm seeing this too. Impossible to get access to the error object directly. It's locked as a string now, of this format `Error: GraphQL error: {...}`. ``` apollo: { errorHandler:...

I'm hoping once this works, I can catch a network error and handle a token refresh call. If anyone has any tips on a better way to handle seamless token...

@rospirski I think your errors are unrelated to the error handler. I made a sandbox showing the error handler not working: https://codesandbox.io/s/apollo-broken-error-handler-499o7

@dmitrijt9 Can you share your config? Weird you need to define it in 2 places.