Open toolness opened 5 years ago
Hey @toolness, thanks for submitting this. This is a reasonable request, however I think keeping the stack trace accessible is important for debugging purposes. We use a pattern within the codebase for printing debug info via this.debug('...')
that should be sufficient. We'd be open to a PR that makes this change!
Seems like an odd choice to make the default level so verbose. Would it be more sensible to pass a --verbose
flag to get the level needed for debugging codegen itself?
Debugging typos is particularly painful with this much output.
In version 2.12.3, running the following with a GraphQL file that has a validation error in it:
produces the following output:
This is extremely verbose and the only line that's really important is the very first one. The
DeprecationWarning
s are also concerning.