VS Code users struggle to review complete, up-to-date diagnostics
VS Code users reported stale diagnostics that did not refresh until they switched tabs, and said reviewing errors could require extra navigation between the editor and the Problems panel. Other requests sought diagnostics for unopened JavaScript and TypeScript files. These reports date from 2017–2018, so the present-day gap needs validation before building.
For javaScript and TypeScript developers using VS Code. Mentioned from Jan 2017 to Apr 2018 on GitHub.
4 different people described this problem in 3 separate discussions.
- Indie fit
- 4.0/10
- Pain
- 4.5/10
- Frequency
- 5.8/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- High
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
For example, I make an error that will be underlined, then to make it go away I have to go to another file tab, then back to the file tab where the error was detected to get vscode to refresh the entire file
There's a lot of issues opened for that feature and not sure if I missed anything or not :smile:
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 4 places to find your first customers
- 2 more quotes from people who have this problem
- Current workarounds, existing solutions and risks