The Wayback Machine - https://web.archive.org/web/20211018084640/https://github.com/topics/static-code-analysis
Skip to content
#

static-code-analysis

Here are 402 public repositories matching this topic...

alvis
alvis commented Sep 24, 2021

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

dvandersluis
dvandersluis commented Sep 16, 2021
~/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.

semgrep
reviewdog
datree
myishay
myishay commented Oct 15, 2021

Is your feature request related to a problem? Please describe.
Installation script supports only x86_64 architecture. 386 and arm64 are not supported.

Describe the solution you'd like
Detect the machine's architecture and download the relevant release in the install script

Additional context
the relevant file that should be changed should be install.sh and `windows_install.p

larastan
Meijuh
Meijuh commented Mar 4, 2021

I am looking for a list of visitors/detectors that I can omit. Specifically, I am look for the allowed values for https://spotbugs.github.io/spotbugs-maven-plugin/spotbugs-mojo.html#omitVisitors.
Previously, in SpotBugs 3.1, this list could be found under "detectors" at e.g. https://spotbugs-in-kengo-toda.readthedocs.io/en/lqc-list-detectors/detectors.html#standard-detectors, but that page/menu

Improve this page

Add a description, image, and links to the static-code-analysis topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the static-code-analysis topic, visit your repo's landing page and select "manage topics."

Learn more