Closed Creative-Difficulty closed 1 year ago
Seems about correct. You can always handle how the errors are rendered with the errorFormatter option
@mcollina This issue is not completed!! This error clogs up memory and wastes space in my logfile. Furthermore, it serves no real purpose as it is just a bunch of gibberish. Could you please provide and example of your option?
Could you please provide and example of your option?
Unfortunately I do not have time right now. There are plenty of examples in Pino, Fastify and Mercurius docs.
Furthermore, it serves no real purpose as it is just a bunch of gibberish.
It clearly states what happened and why. It's not gibberish at all.
No, it doesnt. If you konw it, can you explain it please. The people looking at the logs in production cannot decrypt hyrogliphs
Your attitude is not acceptable in this community. I'm locking this discussion.
I have set up a GraphQL API using mercurius and fastify. Since my app shouldn't support nested Queries, i have implemented a
queryDepth
limiter andNoSchemaIntrospectionCustomRule
(unrelated) like this:The Problem: As soon as i send a test request with a too deep query e.g.:
mercurius
throws this unreasonably long error: