Only critical errors are now underlined
See original GitHub issueIssue is due to a breaking change in coc.nvim. See: https://github.com/neoclide/coc.nvim/issues/3185
What’s the output of :CocCommand pyright.version
coc-pyright 1.1.154 with Pyright 1.1.154
Issue Analytics
- State:
- Created 2 years ago
- Comments:23 (21 by maintainers)
Top Results From Across the Web
Errors are not shown in errors window, nor is problematic ...
After using my solution for a little while, errors stop showing up altogether. Neither in the Error List, nor as underlined text in...
Read more >Turn Off XAML error underlining - visual studio - Stack Overflow
Write xaml in the Extension field and choose XML (Text) Editor from the Editor drop down and then click Add. Your XAML files...
Read more >How To Use Underlined Text To Improve User Experience
A study by the University of Hamburg shows that underlining has a detrimental impact on text readability. Based on the study, avoid underlines...
Read more >Completely Underlined Sentence Correction: Modifiers and Lists
GMAT #GMATPrep #GMATVerbal #GMATSC.
Read more >Outlining text removes underlines (line above and below)
If you put an underline on any text and than go 'Type > Create Outlines', only the text becomes outlined and it completely...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@dob9601 coc used to do a simple hack: if LS returns empty range, for example (3, 3, 3, 3), starts with line 3 char 3, ends with line 3 char 3, coc would add one char to the end, made it to (3, 3, 3, 4). This hack has been removed in https://github.com/neoclide/coc.nvim/pull/3147, this is the breaking change.
Maybe we can add this range format in coc-pyright.
@fannheyward apologies, didn’t see lines 166-174 - thats a great way of handling it, thanks 😃. I’ve got a few other ideas and might make a PR if any work well if that sounds good.
Thanks for the patch either way