-
Notifications
You must be signed in to change notification settings - Fork 789
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
VS: fix unwanted navigation on hover #17592
Conversation
❗ Release notes required
|
@vzarytovskii I don't have much time to test it at the moment, but that's what I'd try. |
I am on leave now and can't test it, but unsure if we return the nav item without showing it, Roslyn will understand it and will switch focus, if it's not a part of its original workspace. And we can't add it to current workspace, since it might break checking. Maybe we can try adding it to miscellaneous files namespace, but then highlighting might break. |
No worries :) I just tested it. Looks like with this change navigation to metadata still works. I can F12 or ctrl+click and I get metadata source with typecheck and semantic colors. I think we don't need to use current workspace. Roslyn creates and uses a separate workspace for metadata as source in their own implementation: |
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
Tested locally. Desired navigation to external metadata still works. Thinking about it, I was getting it during the summer as well, but was contributing it to my fat fingers. (now I know that it only happened when I was copypasting external symbols, and my mouse pointer was above the text). |
Yeah, sorry, it was my hotfix, haven't crossed my mind that hovering can lead to calling definitions API |
Still happens to me in VS2022 17.12 Beta... |
Inserted month ago probably means it's in p3 or release |
Don't show the window, return a nav item instead.
Fixes #17230.