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

When hovering over error show error before api doc. #3772

Closed
bsutton opened this issue Jan 8, 2022 · 1 comment
Closed

When hovering over error show error before api doc. #3772

bsutton opened this issue Jan 8, 2022 · 1 comment
Labels
upstream in vs code / lsp / dap Needs changing in VS Code, LSP or DAP protocols/libraries

Comments

@bsutton
Copy link

bsutton commented Jan 8, 2022

So this one is very much a personal preference thing but I suspect other devs may have the same experience.

When I have a line of code which contains a lint or an error I typically hover over the line to see the error.

The problem is that dart-code displays the api doco and then the error.
The result is that I often need to scroll down to see the error or lint.

My proposal is that if a line contains an error or a lint then that should be displayed followed by the documentation.
So the reverse of what occurs now.

As a second issue the errors seem to be displayed in the wrong order (from least useful to most useful).
The source error always appears to be the last one in the list.
It would be better if they we reversed.

@DanTup
Copy link
Member

DanTup commented Jan 10, 2022

Yep, this would be sensible - but unfortunately it's controlled by VS Code and not the extension :( There's an open issue here (although it's been open for 3 years so doesn't seem like a high priority):

microsoft/vscode#73120

@DanTup DanTup added upstream in vs code / lsp / dap Needs changing in VS Code, LSP or DAP protocols/libraries and removed is enhancement labels Jan 10, 2022
@DanTup DanTup closed this as completed Jan 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upstream in vs code / lsp / dap Needs changing in VS Code, LSP or DAP protocols/libraries
Projects
None yet
Development

No branches or pull requests

2 participants