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
There are currently two main ways to see which warnings can be tracked by ocp-lint: ocp-lint --list gives a list of all known warnings, with a short help text, and .ocplint allows configuring which warnings are enabled, with a more terse documentation (at linter level instead of individual warnings). It is therefore sometimes useful to refer to the output of ocp-lint when editing .ocplint. However, the order in which the plugins are presented differ between both, which makes it difficult to relate both lists. Furthemore, some plugins have pretty different names in both cases (e.g. Source code plugin in ocp-lint --list is plugin_text in .ocplint), which again makes it more difficult to relate plug-ins between both lists.
The text was updated successfully, but these errors were encountered:
There are currently two main ways to see which warnings can be tracked by
ocp-lint
:ocp-lint --list
gives a list of all known warnings, with a short help text, and.ocplint
allows configuring which warnings are enabled, with a more terse documentation (at linter level instead of individual warnings). It is therefore sometimes useful to refer to the output ofocp-lint
when editing.ocplint
. However, the order in which the plugins are presented differ between both, which makes it difficult to relate both lists. Furthemore, some plugins have pretty different names in both cases (e.g.Source code plugin
inocp-lint --list
isplugin_text
in.ocplint
), which again makes it more difficult to relate plug-ins between both lists.The text was updated successfully, but these errors were encountered: