-
-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error.source.context is often too big to be helpful #96
Comments
Sorry for having left this issue unanswered before now. The error What might work is an optional post-processing of the errors and warnings, which would fetch the errors' line positions and drop most of the CST source node data. Optional, so as not to necessitate a major version bump. |
An optional error/warning cleanup step would probably solve this, yes. |
Added the |
generated from commit f6721ec13df9f1eb97d8f53b79a798b61388d035
I'm finding myself in a few cases where error.source.context is a pretty large object. Printing this out (with a logger that includes the source text of functions) results in over 15,000 lines of debugging, which is way too much. Node's built-in console.log() is still several hundred lines.
I can see how this is helpful when working on bugs and features in YAML itself, but it's pretty excessive otherwise. Perhaps it could be omitted when cwd is not the YAML project?
The text was updated successfully, but these errors were encountered: