-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Add goto_next_diag_error
/goto_prev_diag_error
#3405
Comments
This already exists for the current document with |
If I understand correctly, this is only about showing the next error diagnostic, right? |
That makes a lot more sense now! |
Yeah, the diagnostics are great and all, but I'm usually trying to get to the next error first, then I can worry about the diagnostic details. |
I would also like to see this. Using the diagnostic picker in a workspace with hundreds/thousands of warnings requires a lot of scrolling around to find the next error. I think having the diagnostics sorted by severity with errors at the top would make a lot of sense, as finding the next error (arguably the most common task you will be doing when opening the picker) would only require one extra keypress. Then within the severity buckets we could continue to use the current filename sorting. |
There is also #6331, trying to implement the same thing. |
Describe your feature request
Wanted to continue the conversation on going to the next error. I found this extremely useful in another editor and I get really annoyed because I usually have a lot of diagnostic points while I'm working out an issue.
Original Issue
For reference: Pull Request for next diagnostic
The text was updated successfully, but these errors were encountered: