VS Code developers struggle to navigate only relevant diagnostics
VS Code developers want to move through errors, warnings, and informational diagnostics without stopping at items they have filtered out or do not care about. The requests call for navigation by severity and by diagnostic source, while the existing Next/Previous Problem commands are described as too broad. The evidence is several years old, so current VS Code behavior should be checked before building.
For VS Code developers reviewing diagnostics. Mentioned from Sep 2020 to Apr 2024 on GitHub and Hacker News.
7 different people described this problem in 2 separate discussions.
- Indie fit
- 3.0/10
- Pain
- 4.0/10
- Frequency
- 7.5/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
I'd love a feature where I could go to the next error in the file I'm in, or in the entire project, but not the next warning/info marker
I don't think this needs extra configuration. Why can't Next/Previous Problem respect the current filter set in the Problems view? Basically if a problem is filtered out, skip it when doing Next Problem keyboard shortcut
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 3 places to find your first customers
- 6 more quotes from people who have this problem
- Current workarounds, existing solutions and risks