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

Jump to reference when only one reference exists #37346

Open
vsfeedback opened this issue Jul 18, 2019 · 1 comment
Open

Jump to reference when only one reference exists #37346

vsfeedback opened this issue Jul 18, 2019 · 1 comment
Labels
Area-IDE Developer Community The issue was originally reported on https://developercommunity.visualstudio.com Feature Request
Milestone

Comments

@vsfeedback
Copy link

When you are selecting a variable or function you can use the shortcut 'shift + f12' to open the 'references-window'.

It would be great to just skip this window if only one reference exists, and jump immediately to the reference itself.

That way it would work the same as a the default behavior of 'f12' (jump into). If there are multiple references it shows the 'references-window'. If not it goes immediately to the reference itself.

This issue has been moved from https://developercommunity.visualstudio.com/content/idea/556260/jump-to-reference-when-only-one-reference-exists.html
VSTS ticketId: 866911

These are the original issue comments:

Jane Wu [MSFT] on 5/5/2019, 03:09 AM (74 days ago):

Thank you for taking the time to provide your suggestion. We will do some preliminary checks to make sure we can proceed further. We'll provide an update once the issue has been triaged by the product team.

@CyrusNajmabadi
Copy link
Member

The problem here is that we have no idea how many references there actually are. So we're actually searchin for them and populating the list as we find them in an asynchronous manner.

I experimented with this, but it turns out to be complex, especially in the interaction model. i.e. what if the user starts the search, but then starts navigating around or editing themselves. Once we're sure there's a single item, is it ok to just yank them away from what they're doing? What aobut the symbol list? Should we dismiss it because there was only one item? etc. etc.

@jinujoseph jinujoseph added this to the Backlog milestone Jul 18, 2019
@sharwell sharwell added the Developer Community The issue was originally reported on https://developercommunity.visualstudio.com label Nov 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-IDE Developer Community The issue was originally reported on https://developercommunity.visualstudio.com Feature Request
Projects
None yet
Development

No branches or pull requests

4 participants