Skip to content
This repository has been archived by the owner on Jun 7, 2022. It is now read-only.

Better way to handle go to defs when something goes wrong? #71

Open
ryan-blunden opened this issue Jan 11, 2019 · 1 comment
Open

Better way to handle go to defs when something goes wrong? #71

ryan-blunden opened this issue Jan 11, 2019 · 1 comment
Assignees

Comments

@ryan-blunden
Copy link
Contributor

ryan-blunden commented Jan 11, 2019

I'm not sure if the odd behavior is due to the lang extension, the extension API or both, but wanted to document the behavior in any case.

I expected some indication that something went wrong so I know not to wait or try again.

I also expected that the hover would be dismissed after some arbitrary amount of time had passed.

screenflow

@felixfbecker
Copy link
Contributor

Hmm I think this is because the extension polls the server for definitions, which it does because codeintellify will pre-fetch the definition and the server may not have analyzed the project yet. But I think it would be better behaviour to not poll and have the user trigger the action again, but I don't know if that would re-invoke the definition provider. @sqs do you know?

@felixfbecker felixfbecker removed the bug Something isn't working label Jan 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants