| Q |
A |
| Bug report? |
kind of |
| Feature request? |
kind of |
| BC Break report? |
no |
| RFC? |
no |
| Version/Branch |
0.15+ (stable) |
As the doc says: "By default in no debug mode all errors will be logged and replace by a generic error message. Only query parsed error won't be replaced."
https://github.com/overblog/GraphQLBundle/blob/f35dda77dd57179f3696b9217f1a383eb86621b5/docs/error-handling/index.md
I'm trying to ensure that on production, the end user never sees any exceptions, only generic error messages. But I don't see a way to do this for query parse errors, like when I request /graphql and get a "Bad Request: Must provide query parameter". How can those exceptions be replaced?
See also #582
PRs
0.13: #1128 (closed)
0.15: #1131
As the doc says: "By default in no debug mode all errors will be logged and replace by a generic error message. Only query parsed error won't be replaced."
https://github.com/overblog/GraphQLBundle/blob/f35dda77dd57179f3696b9217f1a383eb86621b5/docs/error-handling/index.md
I'm trying to ensure that on production, the end user never sees any exceptions, only generic error messages. But I don't see a way to do this for query parse errors, like when I request /graphql and get a "Bad Request: Must provide query parameter". How can those exceptions be replaced?
See also #582
PRs
0.13: #1128 (closed)
0.15: #1131