-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
Support node ancestors via a configuration option #60
Comments
What about verbose? https://github.com/vfile/vfile-reporter#options, unifiedjs/unified-engine@f44e365 IMO showing URLs here do makes sense, there’s more space here, and there’s links, so you don’t show an entire long ugly URL |
DiagnosticRelatedInformation might be useful for I’d appreciate an example maybe of how the “popups” look with different types of info and settings, maybe it gets crowded quickly? |
One example of diagnostic related information is when you make a TypeScript type error in VSCode. In this screenshot, I like the |
Initial checklist
Problem
Originally posted by @wooorm in #57 (review)
Originally posted by @remcohaszing in #57 (comment)
Originally posted by @wooorm in #57 (comment)
Solution
Add option
showAncestors
. If this is true, the ancestry will be added to the LSP diagnostic message.Alternatives
showAncestors
was chosen arbritrarily. The name could be different.DiagnosticRelatedInformation
instead of appending to the message. This makes the trace clickable, but it renders differently.The text was updated successfully, but these errors were encountered: