You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I suggest to add a new one: (working name) SKIP. So that for instance one can set it as a default level for some inspections. I think that has the potential of simplifying the configuration - i.e. instead of disabling inspections, one would set their level to SKIP.
The text was updated successfully, but these errors were encountered:
It feels like duplication to me.
The use case when one wants to see the issue in the output but not break the build is covered by INFO.
If one would not like to see the issue in the report can be achieved by disabling the inspection.
Do I miss a scenario?
You are right. My point is that the notion of disabling the inspection could be replaced with a new level.
This way we wouldn't need to develop and maintain two separate sets of configuration properties which overlap. E.g. we currently have default values for levels, but no support for a inspection to be disabled by default, etc.
Oh, yes, I see your point.
My thinking led me to the idea of having both, the list of disabled inspections and the new inspection level. What you say is about replacing the disabled list with the inspection level.
It might also play well with the configuration file approach form #439
Current inspection levels are:
ERROR
,WARNING
,INFO
.I suggest to add a new one: (working name)
SKIP
. So that for instance one can set it as a default level for some inspections. I think that has the potential of simplifying the configuration - i.e. instead of disabling inspections, one would set their level toSKIP
.The text was updated successfully, but these errors were encountered: