Code renames are fragile across files and naming styles
Developers need to rename symbols across modules or codebases, but IDE support can be incomplete and broad find-and-replace can miss references or change unintended text. In VS Code, users also report that related names with different casing require separate edits or imprecise replacements. A useful tool could make supported renames easier to review and preserve naming conventions, though it cannot guarantee coverage where a language extension does not provide rename support.
For developers using VS Code and Terraform. Mentioned from Sep 2020 to May 2026 on GitHub and Hacker News.
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.
Even the doFoo to performBar is tedious because you need to catch all instances and your find/replace script strategy might have unintended victims
RealityVoid on Hacker NewsMay 2026Is this being worked on or at least on the roadmap? It's something that is present in other IDE like Jetbrain's PHPStorm, so I am quite surprised it is still not supported on this VS Code extension
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