GraphQL error handling is incompatible with HttpException and Exception Filters about graphql HOT 10 CLOSED

I'm still encountering this issue with the current release! (5.0.0)
Any news how to fix that?

from graphql.

bump

from graphql.

I think the simplest "solution" would be to override the toString method to something like

class HttpException extends Error {
  // ...
  toString() {
    return JSON.stringify(this);
  }
}

this would result in {"mesage":"error...","code":200} instead of [object Object]
@kamilmysliwiec let me know if this seems like a good solution, I can submit a pr

from graphql.

Do you still encounter this issue with the latest release? (4.6.6)

from graphql.

Any Solution?

from graphql.

same here 🤔

from graphql.

also struggling with this (version 6.6.7)

from graphql.

Any Solution? @kamilmysliwiec

from graphql.

Still an issue on 6.5.3. Maybe there is some suggested workaround to make it work with e.g. apollo-link-error? The message field should contain the thrown error message used on the server and communicate that string to the client (instead of the [object Object] response).

from graphql.

This is still an issue, especially when using the Federated GraphQL

from graphql.