Message not propagating in 1.7.1

[prperrino]

Changes between versions 1.5.1 and 1.7.1 appear to have broken the message field propagation when using createError:

const myError = createError('BadError', { message: "This is bad"});
var theError = new myError();
console.log(theError.message)

output of message field is undefined....

Works great in 1.5.1, broken in 1.7.1

[azterix]

I am seeing the same thing. I don't know enough about the history and/or reasoning to use arguments[2] in the ApolloError constructor (instead of using the config variable) to put in a PR for it, but there are only 2 args in the arguments array when I through and the relevant data is in config / arguments[1].

I haven't tried v 1.5.1 myself, but by tweaking that argument reference it works as expected for me.

[thebigredgeek]

Thanks! I'll try to submit a fix for this later tonight

[Ponjimon]

Somehow this only happens if I run it in production mode, locally it works?

[groundmuffin]

Please, fix this )

[Connorelsea]

I am attempting to throw an error inside of a resolver by doing throwing an error created using apollo-errors

const UserDoesntExistError = createError("UserDoesntExist", {
  message: "A user with this email address does not exist",
})
...
if (!user) throw new UserDoesntExistError()

On the frontend when this error occurs, the message is not displayed.

[lobodart]

Any update on this? I had to downgrade to 1.5.1 😞

[joshmanders]

bump

[dakshshah96]

Any updates on this?

[luisgrases]

just created a simple pull request: #32

[luisgrases]

My pull request still doesn't fix all issues so it is better to just use 1.5.1

[ecwyne]

#29 should also fix this issue

[groundmuffin]

i actually lost sleep because of this issue :)

[thebigredgeek]

A fix for this should be live in 1.8.0. Can anyone here confirm?

[joshmanders]

@thebigredgeek confirmed it works.

[ash0080]

@thebigredgeek missing again in 1.9 plz reopen it

[thebigredgeek]

@theGlenn I thought we had a test case for this. confused haha

[pcorey]

I'm also facing this issue. It only seems to happen in production for me. Locally everything works fine.

[thebigredgeek]

@theGlenn did you have a chance to test for this?