static-code-analysis

The version of ESLint you are using.
latest

The problem you want to solve.
improve clarity in docs here https://eslint.org/docs/developer-guide/nodejs-api#-eslintlintfilespatterns

Your take on the correct solution to problem.
Just add a few sentences clarify the differences between Linter and ESLint objects as they have a lot of overlap

**Are you willing to submit a pull

There are some annoying warnings when building the documentation site:

$ antora --pull antora-playbook.yml
asciidoctor: WARNING: skipping reference to missing attribute: 1
asciidoctor: WARNING: skipping reference to missing attribute: 3
asciidoctor: WARNING: skipping reference to missing attribute: word
asciidoctor: WARNING: skipping reference to missing attribute: word
asciidoctor: W

Describe the bug

The --emacs flag doesn't include the human readable message for failing rules in its output, which makes it harder to work out what the appropriate fix is.

(Thanks for semgrep; we're using it for both security analysis and also a few custom rules to catch (non-security) mistakes/typos we keep making. Works well!)

To Reproduce

Run semgrep with the `--emacs

Many repositories need to fix, so please help if you like.

If you could help, it would be helpful if you could comment before starting the work not to overlapping.

Fix example

Run exit command after lint.

echo '::group:: Running golangci-lint with reviewdog 🐶 ...'
go

Affects PMD Version: 6.30.0-SNAPSHOT

Rule: UselessOverridingMethod

Description:

From pmd/pmd#2871 (comment)

Note: There seems to be a difference when having the class in the auxclasspath or not (typeresolution).

Code Sample demonstrating the issue:

Describe the bug
In the docs found here:
https://bandit.readthedocs.io/en/latest/plugins/index.html#complete-test-plugin-listing

B109 and B111 show a description instead of a plugin name. This looks inconsistent since all the other plugin names are listed. I believe this is a result of a recent change to remove these deprecated plugins.

To Reproduce

1. Navigate to https://bandit

e.g.

# map.py
def func(a: int) -> float:
    return float(a)

map(func, ['str'])

$ pytype map.py
Computing dependencies
Analyzing 1 sources with 0 local dependencies
ninja: Entering directory `/[redacted]/.pytype'
ninja: no work to do.
Success: no errors found

while

$ mypy map.py
map.py:5: error: Argument 1 to "map" has incompatible type "Ca

This file is enormous. Also, breaking it up will make running tests faster since Gradle can run separate test classes in parallel.

The Problem

With the new model-property type and ModelPropertyRule Larastan now has the ability to check the existence of model columns that are given to a method.

Adding the model-property type to the Laravel's core methods are done with the help of PHPstan stubs. Some [examples](https://github.com/nunomaduro/larastan/blob/master/stubs/Elo

https://github.com/spotbugs/spotbugs/blob/c9840315b661f8f6d0bcc16acc094ccdfd07b86a/spotbugs/src/main/java/edu/umd/cs/findbugs/ExitCodes.java#L49

This pollutes build logs with a message that users won't care about. Please lower this to debug level.

Workaround: Add -Dorg.slf4j.simpleLogger.log.edu.umd.cs.findbugs.ExitCodes=error to the JVM running Spotbugs.

I wrote some of the code to do this in a branch https://github.com/python-security/pyt/compare/class_based_views, but since I'm working on other things and this feature seems cool and important I'm making this issue 👍

Let me know if you would like any help in implementing.

Justification
It's much more common to see the code below:

Public Sub Foo()
    Dim i, j, k As Long
    'code
End Sub

than it is to see:

Public Sub Foo()
    Dim i As Long, j As Long, k As Long
    'code
End Sub

This is a very common pitfall. Example code in a MultipleDeclarations inspect