JavaScript Warning Classes Corresponding to ESLint Rules

• Introduction
• JavaScript Warning Classes from Built-in ESLint Rules
• Built-In JavaScript Warning Classes
• Enabling and Disabling

Introduction

This page describes the CodeSonar warning classes that are assigned to JavaScript warnings imported from a SARIF file produced by ESLint.

For information on setting up your CodeSonar project to incorporate JavaScript source code and the corresponding ESLint results, see Including JavaScript and TypeScript Components in a CodeSonar Project.

JavaScript Warning Classes from Built-in ESLint Rules

When CodeSonar imports a SARIF file, it determines a corresponding CodeSonar warning class for each rule object in the SARIF rules. If a given warning class does not already exist, the SARIF importer creates it.

There is special handling for SARIF files produced by ESLint.

• CodeSonar ships with a large number of built-in JavaScript warning classes corresponding to messages from ESLint version v8.56.0. Each of these classes has the following properties.
  • The Name is generated using a ESLint-specific mechanism.
  • The Categories include a mnemonic (in the JS.* branch of the CodeSonar mnemonic hierarchy) and a ESLint:<id> category.
• In cases where there is no existing warning class corresponding to a particular rule object in the SARIF rules, the SARIF importer creates a new warning class.
  • The Name is generated using the same ESLint-specific mechanism used for the built-in language warning classes.
  • The Categories include a ESLint:<id> category, but no mnemonic.

Example

Suppose the imported SARIF file includes rule objects like the following.

# ...
    "rules":[
        # ...
        {
          "id": "@typescript-eslint/no-unused-vars",
          # ...
        },
        {
          "id": "no-empty",
          # ...
        },
      # ...
    ],
# ...

CodeSonar identifies the first of these rules ("id": "@typescript-eslint/no-unused-vars") as originating from a typescript-eslint rule, and handles it as described for TypeScript Warning Classes Corresponding to typescript-eslint Rules.

The id for the second rule ("id": "no-empty") does not start with a [plugin_name/] component, so CodeSonar identifies it as originating from a built-in ESLint rule.
(It corresponds to the ESLint no-empty rule.)

1. CodeSonar computes the corresponding warning class name: "No Empty (ESLint)".
2. If there is not already a warning class with this name, CodeSonar creates the warning class. The class categories will be
   • JS.SUGGESTION.NEMPTY (the mnemonic)
     • no-empty belongs to the ESLint Suggestions rule set.
   • ESLint:no-empty
3. CodeSonar creates a "No Empty (ESLint)" warning instance for each result entry in the SARIF that has "ruleId": "no-empty".

SARIF files produced by ESLint

CodeSonar will consider a SARIF file to be produced by ESLint in the following cases.

• The SARIF file was produced and imported via a codesonar es_scan.py invocation.
• The file is imported with a codesonar import_sarif.py invocation that specifies -analyzer eslint.
• The file is imported with a codesonar import_sarif.py invocation that does not specify -analyzer, and the SARIF importer can determine from the file contents that it was produced by ESLint.

In these cases, the SARIF importer determines a corresponding CodeSonar warning class for each rule object in the SARIF rules. The properties for this warning class are shown in the following table.

Built-in JavaScript Warning Classes

These warning classes correspond to built-in rules from ESLint version v8.56.0.

Enabling and Disabling

You have multiple degrees of control over reporting for the warnings issued by ESLint.

• To enable or disable checking for a specific ESLint rule or set of rules (and thus for the corresponding CodeSonar warning class or classes), use your ESLint configuration.

  See the ESLint documentation for details: Configure ESLint .

• To selectively disable submission to the hub for a warning or set of warnings, define a WARNING_FILTER discard rule in a suitable CodeSonar configuration file.

  You can also specify a combination of WARNING_FILTER discard and WARNING_FILTER allow rules, if that is the most convenient way to characterize a specific set. When you specify warning class names (or parts of names) in your WARNING_FILTER rules, make sure you are using the generated CodeSonar warning class name as described above.