Developers struggle to filter noise from call hierarchies
Developers exploring call hierarchies in VS Code can't narrow long result lists by name or source path, so logging calls and test-code references can obscure the calls they want to inspect. They want ways to include or exclude results, such as test folders or production-only code, to make debugging and code exploration easier. Most of this evidence comes from requests on one VS Code issue, rather than independent reports.
For developers exploring code call hierarchies. Mentioned from Jun 2018 to Feb 2024 on GitHub.
6 different people described this problem in 2 separate discussions.
- Indie fit
- 3.0/10
- Pain
- 5.3/10
- Frequency
- 7.0/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- High
What people said
Quoted word for word. Follow a link to read the whole discussion.
We have very long lists of calls and about 90% of the results are log calls, which make it difficult to find other calls
Because, the results include both the main source code and unit tests references, there isn't a way to automatically exclude certain folder directories or paths out from unwanted invocations
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 5 places to find your first customers
- 4 more quotes from people who have this problem
- Current workarounds, existing solutions and risks