Dynamic messages about apollo-errors

[thebigredgeek]

I'm closing this for now, since there doesn't seem to be any interest in moving forward

[thebigredgeek]

You can already override the message when you throw the error, per the docs, with whatever string you want. Does that not handle your use case?

[lucasconstantino]

No, not really. I wouldn't like to send the message always I throw the error, but I would like the message to contain some contextual information. If anyone else finds this useful after all, I can write the pull-request. Until then, I guess I'll keep using my wrapping helper.

[thebigredgeek]

Interesting. I think we could definitely add this to the package, but I am wondering how we ought to make the API work without breaking changes. Any thoughts @lucasconstantino ?

[scf4]

IMO this is more of a UI detail, to be implemented in a client rather than at the API level.

[thebigredgeek]

@scf4 I mostly agree, but I also don't feel overly pained about adding this if enough people want it. I personally render the messages directly in the client, because my current app doesn't have to worry about i18n etc. That said, there is nothing stopping anyone from using a factory function to return errors with dynamic messages without baking any new functionality into the lib.