-
-
Notifications
You must be signed in to change notification settings - Fork 19
Description
IDE and version
WebStorm 2025.2 EAP
Extension version
1.9.0
Biome version
1.9.0
Operating system
- Windows
- macOS
- Linux
Description
I don't know if it's just me or if it is an normal behavior, but Biome error are way too "light", I can't ignore them easily, and I don't even know it's a Biome error.
(When we navigate the three dot menu we can only adjust font size and stuff like that)
Like everytime I have a Biome error that I want to ignore, I need to google the exact error description, and find the exact biome rule name and write "// biome-ignore {rulename}:β¦".
In other similar plugin I can just navigate the popup and click on some "ignore" button

Comparison with Eslint plugin and Typescript plugin
Eslint
When I have an eslint error, the popup tells me that it is eslint, and we can navigate in the popup to ignore the rule for the current file or the current line.
Typescript
When I have a Typescript error, I know that it is typescript, because we can see TSXXXX
, and (typescript XXXX)
And I can navigate in the "more action" menu as well to ignore the error
Steps to reproduce
Just reproduce any biome error, like an empty interface, hover it with your mouse or shortcut
Expected behavior
It should at least specify that it's a biome error, and display the rulename
-An empty interface is equivalent to {}.
+Biome: An empty interface is equivalent to {}.
+lint/suspicious/noEmptyInterface
And it should have a button to ignore the issue ( by adding a // biome-ignore
comment )
I think having the description of the rule could be a good thing as well, because it is not always obvious.
Does this issue occur when using the CLI directly?
Not sure / Not applicable
Link to a minimal reproduction
No response