-
-
Notifications
You must be signed in to change notification settings - Fork 242
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
Allow linters to report warnings #4476
Comments
@nvuillam I just brought the branch to this repository and merge main to bring it from past to present 😅 I will be working on it |
@nvuillam when analyzing this feature I have a doubt that probably has no solution but I raise it.... Many linters in their default output do not differentiate by “log level” (error vs warning) you only get issues with no detail about this. To know that level of detail some have a way to change to other output formats where they already detail in depth this information. The problem is that if we change the default output of the linters we make that the megalinter logs artifacts do not output in a friendly format for the user that checks it... cc @echoix |
@bdovaz I think we can do something like:
I think that SARIF methods should also be updated to count warnings as they count errors Here, we could the number of errors, undepending their level It needs to depending of what we want to count, filter with the num of items in result that have |
@nvuillam I have quite advanced the PR, take a look if you want at what I have so far, I think I don't have much left to fix. |
Right now they only report bugs which is what appears in the reporters:
megalinter/megalinter/Linter.py
Line 130 in 17a5dad
megalinter/megalinter/Linter.py
Line 1381 in 17a5dad
It would be nice to enable that at least warnings are also reported and evaluate if we want some severity level more. Warning severity level is standard, the rest depends on each linter because
vale
linter has “suggestion” level but there are others that will not have it or will be called differently.The text was updated successfully, but these errors were encountered: