microsoft
Support customizing the severity picked up by `problems.decorations.enabled`
When developing, I like to use the "error" problem level for compiler errors, "warning" for linter errors, and "info" for linter warnings. However, sometimes I overlook "info" diagnostics, leading to CI errors (because I use warnings-as-errors, otherwise warnings are just noise). It'd be nice to be able to override the severity reported.
I could also imagine some people wanting to override this to error level, so that they don't get noise from a linter, just compiler errors.
It is the language extension that decide what severity to give to the diagnostic they produce. You have to file an issue against the each language extension.
It is the language extension that decide what severity to give to the diagnostic they produce. You have to file an issue against the each language extension.
I know that. I'm requesting for VS Code to act like infos are warnings (or a separate class) for the problems decorations. In my case, I've customized ESLint to downgrade errors to warnings and warnings to infos, as does Dart tooling, but I'd to make sure I don't miss lints. VS Code doesn't decorate the explorer or tab strip with infos, so it's easy to miss them.
This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!
![vs-code-engineering[bot] avatar](https://avatars.githubusercontent.com/in/281319?v=4 "Published by a pub.dev verified publisher"){kind=small}
This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!
:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!