Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion - searching source for constants. #17334

Closed
hgleaves-ncuadmin opened this issue Dec 15, 2016 · 1 comment
Closed

Suggestion - searching source for constants. #17334

hgleaves-ncuadmin opened this issue Dec 15, 2016 · 1 comment
Labels
*extension-candidate Issue identified as good extension implementation feature-request Request for new features or functionality
Milestone

Comments

@hgleaves-ncuadmin
Copy link

Please consider adding an ability to search all files for constants (for whatever language we're using). Currently Visual Studio (nor VS Code) have this.

The goal here is to:

  • Search for constant strings, ints, floats etc.
  • Right click a constant in the source and offer "Find all references".

This is a gap in the tools, but would be very helpful especially for large legacy solutions where lots of hard coding may have crept in.

We can use Find in Files but this is crude and not able to distinguish true constants in the language from comments or identifier names.

e.g. find all constants "TestUser" would find all ocurrences of that string (but not var TestUser = ... and so on).

Under the hood a constant (in the language like say C#) is more or less a reference to something and so I suppose the Roslyn code could do this.

Thanks

@kieferrm kieferrm added the feature-request Request for new features or functionality label Dec 15, 2016
@kieferrm kieferrm added this to the Backlog milestone Dec 15, 2016
@mjbvz mjbvz added the *extension-candidate Issue identified as good extension implementation label Sep 20, 2018
@vscodebot
Copy link

vscodebot bot commented Sep 20, 2018

We try to keep VS Code lean and we think the functionality you're asking for is great for a VS Code extension. Maybe you can already find one that suits you in the VS Code Marketplace. Just in case, in a few simple steps you can get started writing your own extension. See also our issue reporting guidelines.

Happy Coding!

@vscodebot vscodebot bot closed this as completed Sep 20, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 4, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*extension-candidate Issue identified as good extension implementation feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

3 participants