VS Code users lose time reusing searches and applying replacements
Reports from 2017–2020 describe developers wanting an easier way to retrieve past searches and complex regexes in VS Code, and to replace multiple search results without handling occurrences one by one. A small extension could provide a saved-query workflow or its own replace panel, though fitting neatly into VS Code’s native search controls may be difficult. The reports are old, so whether these gaps remain is worth checking before building.
For VS Code developers who repeatedly search and transform code. Mentioned from Mar 2017 to Mar 2020 on GitHub.
4 different people described this problem in 2 separate discussions.
- Indie fit
- 3.0/10
- Pain
- 5.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.
It's nice to be able to select the complicated regex I want from my search/replace history list visually, rather than scrolling through them one by one. Especially when applying them in sequence to perform some complex file transform
Having a replace field in the search editor would permit to quickly replace all occurence without having to manage each occurence
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 3 places to find your first customers
- 2 more quotes from people who have this problem
- Current workarounds, existing solutions and risks