static-code-analysis

What rule do you want to change?

max-lines-per-function

What change to do you want to make?

Generate fewer warnings

How do you think the change should be implemented?

A new default behavior

Example code

/* eslint max-lines-per-function: ["error", {"max": 3}] */
export function bulkyFunction() {
  // line 1
  // line 2
  // line 3
}

Wha

~/code/rubocop$ grep -iro "autocorrect" . | wc -l
    1971
~/code/rubocop$ grep -iro "auto-correct" . | wc -l
    1551

Both autocorrect and auto-correct are used frequently in RuboCop. Should we be consistent? If so, which one?

Any change should only affect comments and other string content, not method names.

Describe the bug

I expect metavariables between backticks to work in JavaScript:

$ semgrep --lang js -e '`$A`'
ran 1 rules on 1 files: 0 findings

I expect this to match the following:

`test`;

Priority
How important is this to you?

• P2: annoying but not blocking me

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

Elm has the option to output errors as JSON (via a flag), and something like that is handy for writing tooling around it. I'm trying to integrate pytype into ALE and this would make it a lot easier.

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

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

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
Release versions should not contain debugging support files.

Description
These files add 13MB of junk to the installation that shouldn't be there for normal users. The purpose of these files is to debug release builds. They shouldn't be included in the final installation.

The total install folder is 29.3MB so the PDB files make up %44 of the installation size.

![i