-
Notifications
You must be signed in to change notification settings - Fork 30.4k
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
Find usages (find all file references / find all folder references) #66162
Comments
(Experimental duplicate detection) |
I spent one day for this, and the result was no way to achieve it. |
@jabacchetta Was there any progress on this? For me, in simple ES6 code with If I right click the |
The features that I've requested here haven't been added yet, but what you're describing should work, if I understand correctly. Are you importing Edit: Woops, just noticed that you already solved your problem in issue above. |
It only works after adding |
This is the single biggest disappointment coming from WebStorm. VSCode wins in so many ways. The two areas that cause weekly pain are:
|
Finally in the backlog, which will take like 2 years or more. But at least there's a milestone. I can't believe people can keep using VSCode without a proper "find usages". It is the only reason I still stick with Sublime Text. |
for now i found this solution but is really overkill and need a lot of configuration https://github.com/pahen/madge Hope to see a search files ref relations soon ! |
Very useful feature |
Any news about this feature? 2 years past, still very much in need of it! |
I often think that vscode had already implememted find variable/type reference, why not imllements file reference. It should be easier. |
"Find usages" for a function is also missing. How do you develop without that? |
@liisi29 That already exists: right click on the function and select |
Correct me if I'm wrong (and I really hope I am), but this only finds references in ONE file. Not in the whole application. |
By default without |
Very useful feature. I have many outdated resources in my project that may no longer be referenced, but It's hard to find them all. |
Doesn't work for Package info:
|
Used this # wrap to alias function for easy usage
findstr () { grep -r -n -I "$1" ./; }
# usage example
findstr wp-service |
If you search the issues here on GitHub and on StackOverflow, you'll find that there is a ton of fragmentation around this feature for a few reasons:
This feature refers to three subsets of finding references:
1. Find all references of a symbol
VSCode has this already.
2. Find all references of a file
VSCode has this already, but few know about it, and the process for getting to it is unnecessary. Currently you need to use the "find all references" command on an import path that includes the file.
This is a very useful feature, and should be made available in the file explorer, for a file's context menu when right clicking it, as explained here. Additionally, there should be a command,
References: Find All References of File
as explained here.3. Find all references of a folder
VSCode does not yet have this feature. When using this on a folder (made available in the context menu), it should show the references for all files inside that folder. A command might be useful here as well (
References: Find All References of Folder
).Note:
I've already submitted a feature request mentioning this in the past, which was closed and suggested as an extension. However, it looks like I wasn't clear on what my request was, because VSCode has since implemented a lot of this functionality. And it's also clear that there's a lot of confusion around this among VSCode users.
The text was updated successfully, but these errors were encountered: