InsidersByte/react-markdown-renderer

View on GitHub

Showing 61 of 61 total issues

File eslint_vx.x.x.js has 2019 lines of code (exceeds 250 allowed). Consider refactoring.
Open

// flow-typed signature: 1680ab41ccc1eefa1183d9587ccd9a39
// flow-typed version: <<STUB>>/eslint_v4.3.0/flow_v0.51.1

/**
 * This is an autogenerated libdef stub for:
Severity: Major
Found in flow-typed/npm/eslint_vx.x.x.js - About 5 days to fix

    File react-test-renderer_vx.x.x.js has 1509 lines of code (exceeds 250 allowed). Consider refactoring.
    Open

    // flow-typed signature: ad93bcbd778a7fb1b69fd7e0ea61ec04
    // flow-typed version: <<STUB>>/react-test-renderer_v15.6.1/flow_v0.51.1
    
    /**
     * This is an autogenerated libdef stub for:
    Severity: Major
    Found in flow-typed/npm/react-test-renderer_vx.x.x.js - About 4 days to fix

      File eslint-plugin-jsx-a11y_vx.x.x.js has 1395 lines of code (exceeds 250 allowed). Consider refactoring.
      Open

      // flow-typed signature: c85e1c6104a993aea7ba96bcf1b34da9
      // flow-typed version: <<STUB>>/eslint-plugin-jsx-a11y_v5.1.1/flow_v0.51.1
      
      /**
       * This is an autogenerated libdef stub for:
      Severity: Major
      Found in flow-typed/npm/eslint-plugin-jsx-a11y_vx.x.x.js - About 3 days to fix

        File eslint-plugin-react_vx.x.x.js has 423 lines of code (exceeds 250 allowed). Consider refactoring.
        Open

        // flow-typed signature: b59bd40cb3f64d1ba0653e975c073412
        // flow-typed version: <<STUB>>/eslint-plugin-react_v7.1.0/flow_v0.51.1
        
        /**
         * This is an autogenerated libdef stub for:
        Severity: Minor
        Found in flow-typed/npm/eslint-plugin-react_vx.x.x.js - About 6 hrs to fix

          File autoprefixer_vx.x.x.js has 369 lines of code (exceeds 250 allowed). Consider refactoring.
          Open

          // flow-typed signature: 5be4a365acb85b5337cbdbcef1bc306a
          // flow-typed version: <<STUB>>/autoprefixer_v7.1.2/flow_v0.51.1
          
          /**
           * This is an autogenerated libdef stub for:
          Severity: Minor
          Found in flow-typed/npm/autoprefixer_vx.x.x.js - About 4 hrs to fix

            File eslint-plugin-import_vx.x.x.js has 267 lines of code (exceeds 250 allowed). Consider refactoring.
            Open

            // flow-typed signature: 371f6514993e9912df8d225b969b4397
            // flow-typed version: <<STUB>>/eslint-plugin-import_v2.7.0/flow_v0.51.1
            
            /**
             * This is an autogenerated libdef stub for:
            Severity: Minor
            Found in flow-typed/npm/eslint-plugin-import_vx.x.x.js - About 2 hrs to fix

              Similar blocks of code found in 2 locations. Consider refactoring.
              Open

                      it('if nothing passed', () => {
                        shallow(<MarkdownRenderer markdown="# This is a H1" />);
              
                        expect(remarkable).toHaveBeenCalledTimes(1);
                        expect(remarkable).toHaveBeenCalledWith('default', {});
              Severity: Major
              Found in src/index.test.js and 1 other location - About 1 hr to fix
              src/index.test.js on lines 69..74

              Duplicated Code

              Duplicated code can lead to software that is hard to understand and difficult to change. The Don't Repeat Yourself (DRY) principle states:

              Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.

              When you violate DRY, bugs and maintenance problems are sure to follow. Duplicated code has a tendency to both continue to replicate and also to diverge (leaving bugs as two similar implementations differ in subtle ways).

              Tuning

              This issue has a mass of 63.

              We set useful threshold defaults for the languages we support but you may want to adjust these settings based on your project guidelines.

              The threshold configuration represents the minimum mass a code block must have to be analyzed for duplication. The lower the threshold, the more fine-grained the comparison.

              If the engine is too easily reporting duplication, try raising the threshold. If you suspect that the engine isn't catching enough duplication, try lowering the threshold. The best setting tends to differ from language to language.

              See codeclimate-duplication's documentation for more information about tuning the mass threshold in your .codeclimate.yml.

              Refactorings

              Further Reading

              Similar blocks of code found in 2 locations. Consider refactoring.
              Open

                    it('should default to empty object', () => {
                      shallow(<MarkdownRenderer markdown="# This is a H1" />);
              
                      expect(remarkable).toHaveBeenCalledTimes(1);
                      expect(remarkable).toHaveBeenCalledWith('default', {});
              Severity: Major
              Found in src/index.test.js and 1 other location - About 1 hr to fix
              src/index.test.js on lines 33..38

              Duplicated Code

              Duplicated code can lead to software that is hard to understand and difficult to change. The Don't Repeat Yourself (DRY) principle states:

              Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.

              When you violate DRY, bugs and maintenance problems are sure to follow. Duplicated code has a tendency to both continue to replicate and also to diverge (leaving bugs as two similar implementations differ in subtle ways).

              Tuning

              This issue has a mass of 63.

              We set useful threshold defaults for the languages we support but you may want to adjust these settings based on your project guidelines.

              The threshold configuration represents the minimum mass a code block must have to be analyzed for duplication. The lower the threshold, the more fine-grained the comparison.

              If the engine is too easily reporting duplication, try raising the threshold. If you suspect that the engine isn't catching enough duplication, try lowering the threshold. The best setting tends to differ from language to language.

              See codeclimate-duplication's documentation for more information about tuning the mass threshold in your .codeclimate.yml.

              Refactorings

              Further Reading

              Identical blocks of code found in 2 locations. Consider refactoring.
              Open

                  withTheme: <T: {}, C: Component<*>>(component: C) => (C & Component<{ theme: T }>),
              Severity: Major
              Found in flow-typed/npm/styled-components_v2.x.x.js and 1 other location - About 1 hr to fix
              flow-typed/npm/styled-components_v2.x.x.js on lines 56..56

              Duplicated Code

              Duplicated code can lead to software that is hard to understand and difficult to change. The Don't Repeat Yourself (DRY) principle states:

              Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.

              When you violate DRY, bugs and maintenance problems are sure to follow. Duplicated code has a tendency to both continue to replicate and also to diverge (leaving bugs as two similar implementations differ in subtle ways).

              Tuning

              This issue has a mass of 60.

              We set useful threshold defaults for the languages we support but you may want to adjust these settings based on your project guidelines.

              The threshold configuration represents the minimum mass a code block must have to be analyzed for duplication. The lower the threshold, the more fine-grained the comparison.

              If the engine is too easily reporting duplication, try raising the threshold. If you suspect that the engine isn't catching enough duplication, try lowering the threshold. The best setting tends to differ from language to language.

              See codeclimate-duplication's documentation for more information about tuning the mass threshold in your .codeclimate.yml.

              Refactorings

              Further Reading

              Identical blocks of code found in 2 locations. Consider refactoring.
              Open

                  withTheme: <T: {}, C: Component<*>>(component: C) => (C & Component<{ theme: T }>),
              Severity: Major
              Found in flow-typed/npm/styled-components_v2.x.x.js and 1 other location - About 1 hr to fix
              flow-typed/npm/styled-components_v2.x.x.js on lines 210..210

              Duplicated Code

              Duplicated code can lead to software that is hard to understand and difficult to change. The Don't Repeat Yourself (DRY) principle states:

              Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.

              When you violate DRY, bugs and maintenance problems are sure to follow. Duplicated code has a tendency to both continue to replicate and also to diverge (leaving bugs as two similar implementations differ in subtle ways).

              Tuning

              This issue has a mass of 60.

              We set useful threshold defaults for the languages we support but you may want to adjust these settings based on your project guidelines.

              The threshold configuration represents the minimum mass a code block must have to be analyzed for duplication. The lower the threshold, the more fine-grained the comparison.

              If the engine is too easily reporting duplication, try raising the threshold. If you suspect that the engine isn't catching enough duplication, try lowering the threshold. The best setting tends to differ from language to language.

              See codeclimate-duplication's documentation for more information about tuning the mass threshold in your .codeclimate.yml.

              Refactorings

              Further Reading

              Similar blocks of code found in 2 locations. Consider refactoring.
              Open

                  reduce<T>(fn: (value: T, node: this, index: number) => T, initialValue?: T): Array<T>;
              Severity: Minor
              Found in flow-typed/npm/enzyme_v2.3.x.js and 1 other location - About 55 mins to fix
              flow-typed/npm/enzyme_v2.3.x.js on lines 62..62

              Duplicated Code

              Duplicated code can lead to software that is hard to understand and difficult to change. The Don't Repeat Yourself (DRY) principle states:

              Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.

              When you violate DRY, bugs and maintenance problems are sure to follow. Duplicated code has a tendency to both continue to replicate and also to diverge (leaving bugs as two similar implementations differ in subtle ways).

              Tuning

              This issue has a mass of 54.

              We set useful threshold defaults for the languages we support but you may want to adjust these settings based on your project guidelines.

              The threshold configuration represents the minimum mass a code block must have to be analyzed for duplication. The lower the threshold, the more fine-grained the comparison.

              If the engine is too easily reporting duplication, try raising the threshold. If you suspect that the engine isn't catching enough duplication, try lowering the threshold. The best setting tends to differ from language to language.

              See codeclimate-duplication's documentation for more information about tuning the mass threshold in your .codeclimate.yml.

              Refactorings

              Further Reading

              Similar blocks of code found in 2 locations. Consider refactoring.
              Open

                  reduceRight<T>(fn: (value: T, node: this, index: number) => T, initialValue?: T): Array<T>;
              Severity: Minor
              Found in flow-typed/npm/enzyme_v2.3.x.js and 1 other location - About 55 mins to fix
              flow-typed/npm/enzyme_v2.3.x.js on lines 61..61

              Duplicated Code

              Duplicated code can lead to software that is hard to understand and difficult to change. The Don't Repeat Yourself (DRY) principle states:

              Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.

              When you violate DRY, bugs and maintenance problems are sure to follow. Duplicated code has a tendency to both continue to replicate and also to diverge (leaving bugs as two similar implementations differ in subtle ways).

              Tuning

              This issue has a mass of 54.

              We set useful threshold defaults for the languages we support but you may want to adjust these settings based on your project guidelines.

              The threshold configuration represents the minimum mass a code block must have to be analyzed for duplication. The lower the threshold, the more fine-grained the comparison.

              If the engine is too easily reporting duplication, try raising the threshold. If you suspect that the engine isn't catching enough duplication, try lowering the threshold. The best setting tends to differ from language to language.

              See codeclimate-duplication's documentation for more information about tuning the mass threshold in your .codeclimate.yml.

              Refactorings

              Further Reading

              Similar blocks of code found in 2 locations. Consider refactoring.
              Open

              const AdvancedUsage = () =>
                <Root>
                  <Title>Options</Title>
              
                  <LiveEdit code={code} />
              Severity: Minor
              Found in docs/src/Options.js and 1 other location - About 40 mins to fix
              docs/src/BasicUsage.js on lines 24..29

              Duplicated Code

              Duplicated code can lead to software that is hard to understand and difficult to change. The Don't Repeat Yourself (DRY) principle states:

              Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.

              When you violate DRY, bugs and maintenance problems are sure to follow. Duplicated code has a tendency to both continue to replicate and also to diverge (leaving bugs as two similar implementations differ in subtle ways).

              Tuning

              This issue has a mass of 49.

              We set useful threshold defaults for the languages we support but you may want to adjust these settings based on your project guidelines.

              The threshold configuration represents the minimum mass a code block must have to be analyzed for duplication. The lower the threshold, the more fine-grained the comparison.

              If the engine is too easily reporting duplication, try raising the threshold. If you suspect that the engine isn't catching enough duplication, try lowering the threshold. The best setting tends to differ from language to language.

              See codeclimate-duplication's documentation for more information about tuning the mass threshold in your .codeclimate.yml.

              Refactorings

              Further Reading

              Similar blocks of code found in 2 locations. Consider refactoring.
              Open

              const BasicUsage = () =>
                <Root>
                  <Title>Basic Usage</Title>
              
                  <LiveEdit code={code} />
              Severity: Minor
              Found in docs/src/BasicUsage.js and 1 other location - About 40 mins to fix
              docs/src/Options.js on lines 46..51

              Duplicated Code

              Duplicated code can lead to software that is hard to understand and difficult to change. The Don't Repeat Yourself (DRY) principle states:

              Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.

              When you violate DRY, bugs and maintenance problems are sure to follow. Duplicated code has a tendency to both continue to replicate and also to diverge (leaving bugs as two similar implementations differ in subtle ways).

              Tuning

              This issue has a mass of 49.

              We set useful threshold defaults for the languages we support but you may want to adjust these settings based on your project guidelines.

              The threshold configuration represents the minimum mass a code block must have to be analyzed for duplication. The lower the threshold, the more fine-grained the comparison.

              If the engine is too easily reporting duplication, try raising the threshold. If you suspect that the engine isn't catching enough duplication, try lowering the threshold. The best setting tends to differ from language to language.

              See codeclimate-duplication's documentation for more information about tuning the mass threshold in your .codeclimate.yml.

              Refactorings

              Further Reading

              'beforeEach' is defined but never used.
              Open

              declare function beforeEach(fn: Function): void;
              Severity: Minor
              Found in flow-typed/npm/jest_v20.x.x.js by eslint

              Disallow Unused Variables (no-unused-vars)

              Variables that are declared and not used anywhere in the code are most likely an error due to incomplete refactoring. Such variables take up space in the code and can lead to confusion by readers.

              Rule Details

              This rule is aimed at eliminating unused variables, functions, and parameters of functions.

              A variable is considered to be used if any of the following are true:

              • It represents a function that is called (doSomething())
              • It is read (var y = x)
              • It is passed into a function as an argument (doSomething(x))
              • It is read inside of a function that is passed to another function (doSomething(function() { foo(); }))

              A variable is not considered to be used if it is only ever assigned to (var x = 5) or declared.

              Examples of incorrect code for this rule:

              /*eslint no-unused-vars: "error"*/
              /*global some_unused_var*/
              
              // It checks variables you have defined as global
              some_unused_var = 42;
              
              var x;
              
              // Write-only variables are not considered as used.
              var y = 10;
              y = 5;
              
              // A read for a modification of itself is not considered as used.
              var z = 0;
              z = z + 1;
              
              // By default, unused arguments cause warnings.
              (function(foo) {
                  return 5;
              })();
              
              // Unused recursive functions also cause warnings.
              function fact(n) {
                  if (n < 2) return 1;
                  return n * fact(n - 1);
              }
              
              // When a function definition destructures an array, unused entries from the array also cause warnings.
              function getY([x, y]) {
                  return y;
              }

              Examples of correct code for this rule:

              /*eslint no-unused-vars: "error"*/
              
              var x = 10;
              alert(x);
              
              // foo is considered used here
              myFunc(function foo() {
                  // ...
              }.bind(this));
              
              (function(foo) {
                  return foo;
              })();
              
              var myFunc;
              myFunc = setTimeout(function() {
                  // myFunc is considered used
                  myFunc();
              }, 50);
              
              // Only the second argument from the descructured array is used.
              function getY([, y]) {
                  return y;
              }

              exported

              In environments outside of CommonJS or ECMAScript modules, you may use var to create a global variable that may be used by other scripts. You can use the /* exported variableName */ comment block to indicate that this variable is being exported and therefore should not be considered unused.

              Note that /* exported */ has no effect for any of the following:

              • when the environment is node or commonjs
              • when parserOptions.sourceType is module
              • when ecmaFeatures.globalReturn is true

              The line comment // exported variableName will not work as exported is not line-specific.

              Examples of correct code for /* exported variableName */ operation:

              /* exported global_var */
              
              var global_var = 42;

              Options

              This rule takes one argument which can be a string or an object. The string settings are the same as those of the vars property (explained below).

              By default this rule is enabled with all option for variables and after-used for arguments.

              {
                  "rules": {
                      "no-unused-vars": ["error", { "vars": "all", "args": "after-used", "ignoreRestSiblings": false }]
                  }
              }

              vars

              The vars option has two settings:

              • all checks all variables for usage, including those in the global scope. This is the default setting.
              • local checks only that locally-declared variables are used but will allow global variables to be unused.

              vars: local

              Examples of correct code for the { "vars": "local" } option:

              /*eslint no-unused-vars: ["error", { "vars": "local" }]*/
              /*global some_unused_var */
              
              some_unused_var = 42;

              varsIgnorePattern

              The varsIgnorePattern option specifies exceptions not to check for usage: variables whose names match a regexp pattern. For example, variables whose names contain ignored or Ignored.

              Examples of correct code for the { "varsIgnorePattern": "[iI]gnored" } option:

              /*eslint no-unused-vars: ["error", { "varsIgnorePattern": "[iI]gnored" }]*/
              
              var firstVarIgnored = 1;
              var secondVar = 2;
              console.log(secondVar);

              args

              The args option has three settings:

              • after-used - only the last argument must be used. This allows you, for instance, to have two named parameters to a function and as long as you use the second argument, ESLint will not warn you about the first. This is the default setting.
              • all - all named arguments must be used.
              • none - do not check arguments.

              args: after-used

              Examples of incorrect code for the default { "args": "after-used" } option:

              /*eslint no-unused-vars: ["error", { "args": "after-used" }]*/
              
              // 1 error
              // "baz" is defined but never used
              (function(foo, bar, baz) {
                  return bar;
              })();

              Examples of correct code for the default { "args": "after-used" } option:

              /*eslint no-unused-vars: ["error", {"args": "after-used"}]*/
              
              (function(foo, bar, baz) {
                  return baz;
              })();

              args: all

              Examples of incorrect code for the { "args": "all" } option:

              /*eslint no-unused-vars: ["error", { "args": "all" }]*/
              
              // 2 errors
              // "foo" is defined but never used
              // "baz" is defined but never used
              (function(foo, bar, baz) {
                  return bar;
              })();

              args: none

              Examples of correct code for the { "args": "none" } option:

              /*eslint no-unused-vars: ["error", { "args": "none" }]*/
              
              (function(foo, bar, baz) {
                  return bar;
              })();

              ignoreRestSiblings

              The ignoreRestSiblings option is a boolean (default: false). Using a Rest Property it is possible to "omit" properties from an object, but by default the sibling properties are marked as "unused". With this option enabled the rest property's siblings are ignored.

              Examples of correct code for the { "ignoreRestSiblings": true } option:

              /*eslint no-unused-vars: ["error", { "ignoreRestSiblings": true }]*/
              // 'type' is ignored because it has a rest property sibling.
              var { type, ...coords } = data;

              argsIgnorePattern

              The argsIgnorePattern option specifies exceptions not to check for usage: arguments whose names match a regexp pattern. For example, variables whose names begin with an underscore.

              Examples of correct code for the { "argsIgnorePattern": "^_" } option:

              /*eslint no-unused-vars: ["error", { "argsIgnorePattern": "^_" }]*/
              
              function foo(x, _y) {
                  return x + 1;
              }
              foo();

              caughtErrors

              The caughtErrors option is used for catch block arguments validation.

              It has two settings:

              • none - do not check error objects. This is the default setting.
              • all - all named arguments must be used.

              caughtErrors: none

              Not specifying this rule is equivalent of assigning it to none.

              Examples of correct code for the { "caughtErrors": "none" } option:

              /*eslint no-unused-vars: ["error", { "caughtErrors": "none" }]*/
              
              try {
                  //...
              } catch (err) {
                  console.error("errors");
              }

              caughtErrors: all

              Examples of incorrect code for the { "caughtErrors": "all" } option:

              /*eslint no-unused-vars: ["error", { "caughtErrors": "all" }]*/
              
              // 1 error
              // "err" is defined but never used
              try {
                  //...
              } catch (err) {
                  console.error("errors");
              }

              caughtErrorsIgnorePattern

              The caughtErrorsIgnorePattern option specifies exceptions not to check for usage: catch arguments whose names match a regexp pattern. For example, variables whose names begin with a string 'ignore'.

              Examples of correct code for the { "caughtErrorsIgnorePattern": "^ignore" } option:

              /*eslint no-unused-vars: ["error", { "caughtErrorsIgnorePattern": "^ignore" }]*/
              
              try {
                  //...
              } catch (ignoreErr) {
                  console.error("errors");
              }

              When Not To Use It

              If you don't want to be notified about unused variables or function arguments, you can safely turn this rule off. Source: http://eslint.org/docs/rules/

              'xit' is defined but never used.
              Open

              declare var xit: typeof it;
              Severity: Minor
              Found in flow-typed/npm/jest_v20.x.x.js by eslint

              Disallow Unused Variables (no-unused-vars)

              Variables that are declared and not used anywhere in the code are most likely an error due to incomplete refactoring. Such variables take up space in the code and can lead to confusion by readers.

              Rule Details

              This rule is aimed at eliminating unused variables, functions, and parameters of functions.

              A variable is considered to be used if any of the following are true:

              • It represents a function that is called (doSomething())
              • It is read (var y = x)
              • It is passed into a function as an argument (doSomething(x))
              • It is read inside of a function that is passed to another function (doSomething(function() { foo(); }))

              A variable is not considered to be used if it is only ever assigned to (var x = 5) or declared.

              Examples of incorrect code for this rule:

              /*eslint no-unused-vars: "error"*/
              /*global some_unused_var*/
              
              // It checks variables you have defined as global
              some_unused_var = 42;
              
              var x;
              
              // Write-only variables are not considered as used.
              var y = 10;
              y = 5;
              
              // A read for a modification of itself is not considered as used.
              var z = 0;
              z = z + 1;
              
              // By default, unused arguments cause warnings.
              (function(foo) {
                  return 5;
              })();
              
              // Unused recursive functions also cause warnings.
              function fact(n) {
                  if (n < 2) return 1;
                  return n * fact(n - 1);
              }
              
              // When a function definition destructures an array, unused entries from the array also cause warnings.
              function getY([x, y]) {
                  return y;
              }

              Examples of correct code for this rule:

              /*eslint no-unused-vars: "error"*/
              
              var x = 10;
              alert(x);
              
              // foo is considered used here
              myFunc(function foo() {
                  // ...
              }.bind(this));
              
              (function(foo) {
                  return foo;
              })();
              
              var myFunc;
              myFunc = setTimeout(function() {
                  // myFunc is considered used
                  myFunc();
              }, 50);
              
              // Only the second argument from the descructured array is used.
              function getY([, y]) {
                  return y;
              }

              exported

              In environments outside of CommonJS or ECMAScript modules, you may use var to create a global variable that may be used by other scripts. You can use the /* exported variableName */ comment block to indicate that this variable is being exported and therefore should not be considered unused.

              Note that /* exported */ has no effect for any of the following:

              • when the environment is node or commonjs
              • when parserOptions.sourceType is module
              • when ecmaFeatures.globalReturn is true

              The line comment // exported variableName will not work as exported is not line-specific.

              Examples of correct code for /* exported variableName */ operation:

              /* exported global_var */
              
              var global_var = 42;

              Options

              This rule takes one argument which can be a string or an object. The string settings are the same as those of the vars property (explained below).

              By default this rule is enabled with all option for variables and after-used for arguments.

              {
                  "rules": {
                      "no-unused-vars": ["error", { "vars": "all", "args": "after-used", "ignoreRestSiblings": false }]
                  }
              }

              vars

              The vars option has two settings:

              • all checks all variables for usage, including those in the global scope. This is the default setting.
              • local checks only that locally-declared variables are used but will allow global variables to be unused.

              vars: local

              Examples of correct code for the { "vars": "local" } option:

              /*eslint no-unused-vars: ["error", { "vars": "local" }]*/
              /*global some_unused_var */
              
              some_unused_var = 42;

              varsIgnorePattern

              The varsIgnorePattern option specifies exceptions not to check for usage: variables whose names match a regexp pattern. For example, variables whose names contain ignored or Ignored.

              Examples of correct code for the { "varsIgnorePattern": "[iI]gnored" } option:

              /*eslint no-unused-vars: ["error", { "varsIgnorePattern": "[iI]gnored" }]*/
              
              var firstVarIgnored = 1;
              var secondVar = 2;
              console.log(secondVar);

              args

              The args option has three settings:

              • after-used - only the last argument must be used. This allows you, for instance, to have two named parameters to a function and as long as you use the second argument, ESLint will not warn you about the first. This is the default setting.
              • all - all named arguments must be used.
              • none - do not check arguments.

              args: after-used

              Examples of incorrect code for the default { "args": "after-used" } option:

              /*eslint no-unused-vars: ["error", { "args": "after-used" }]*/
              
              // 1 error
              // "baz" is defined but never used
              (function(foo, bar, baz) {
                  return bar;
              })();

              Examples of correct code for the default { "args": "after-used" } option:

              /*eslint no-unused-vars: ["error", {"args": "after-used"}]*/
              
              (function(foo, bar, baz) {
                  return baz;
              })();

              args: all

              Examples of incorrect code for the { "args": "all" } option:

              /*eslint no-unused-vars: ["error", { "args": "all" }]*/
              
              // 2 errors
              // "foo" is defined but never used
              // "baz" is defined but never used
              (function(foo, bar, baz) {
                  return bar;
              })();

              args: none

              Examples of correct code for the { "args": "none" } option:

              /*eslint no-unused-vars: ["error", { "args": "none" }]*/
              
              (function(foo, bar, baz) {
                  return bar;
              })();

              ignoreRestSiblings

              The ignoreRestSiblings option is a boolean (default: false). Using a Rest Property it is possible to "omit" properties from an object, but by default the sibling properties are marked as "unused". With this option enabled the rest property's siblings are ignored.

              Examples of correct code for the { "ignoreRestSiblings": true } option:

              /*eslint no-unused-vars: ["error", { "ignoreRestSiblings": true }]*/
              // 'type' is ignored because it has a rest property sibling.
              var { type, ...coords } = data;

              argsIgnorePattern

              The argsIgnorePattern option specifies exceptions not to check for usage: arguments whose names match a regexp pattern. For example, variables whose names begin with an underscore.

              Examples of correct code for the { "argsIgnorePattern": "^_" } option:

              /*eslint no-unused-vars: ["error", { "argsIgnorePattern": "^_" }]*/
              
              function foo(x, _y) {
                  return x + 1;
              }
              foo();

              caughtErrors

              The caughtErrors option is used for catch block arguments validation.

              It has two settings:

              • none - do not check error objects. This is the default setting.
              • all - all named arguments must be used.

              caughtErrors: none

              Not specifying this rule is equivalent of assigning it to none.

              Examples of correct code for the { "caughtErrors": "none" } option:

              /*eslint no-unused-vars: ["error", { "caughtErrors": "none" }]*/
              
              try {
                  //...
              } catch (err) {
                  console.error("errors");
              }

              caughtErrors: all

              Examples of incorrect code for the { "caughtErrors": "all" } option:

              /*eslint no-unused-vars: ["error", { "caughtErrors": "all" }]*/
              
              // 1 error
              // "err" is defined but never used
              try {
                  //...
              } catch (err) {
                  console.error("errors");
              }

              caughtErrorsIgnorePattern

              The caughtErrorsIgnorePattern option specifies exceptions not to check for usage: catch arguments whose names match a regexp pattern. For example, variables whose names begin with a string 'ignore'.

              Examples of correct code for the { "caughtErrorsIgnorePattern": "^ignore" } option:

              /*eslint no-unused-vars: ["error", { "caughtErrorsIgnorePattern": "^ignore" }]*/
              
              try {
                  //...
              } catch (ignoreErr) {
                  console.error("errors");
              }

              When Not To Use It

              If you don't want to be notified about unused variables or function arguments, you can safely turn this rule off. Source: http://eslint.org/docs/rules/

              'afterAll' is defined but never used.
              Open

              declare function afterAll(fn: Function): void;
              Severity: Minor
              Found in flow-typed/npm/jest_v20.x.x.js by eslint

              Disallow Unused Variables (no-unused-vars)

              Variables that are declared and not used anywhere in the code are most likely an error due to incomplete refactoring. Such variables take up space in the code and can lead to confusion by readers.

              Rule Details

              This rule is aimed at eliminating unused variables, functions, and parameters of functions.

              A variable is considered to be used if any of the following are true:

              • It represents a function that is called (doSomething())
              • It is read (var y = x)
              • It is passed into a function as an argument (doSomething(x))
              • It is read inside of a function that is passed to another function (doSomething(function() { foo(); }))

              A variable is not considered to be used if it is only ever assigned to (var x = 5) or declared.

              Examples of incorrect code for this rule:

              /*eslint no-unused-vars: "error"*/
              /*global some_unused_var*/
              
              // It checks variables you have defined as global
              some_unused_var = 42;
              
              var x;
              
              // Write-only variables are not considered as used.
              var y = 10;
              y = 5;
              
              // A read for a modification of itself is not considered as used.
              var z = 0;
              z = z + 1;
              
              // By default, unused arguments cause warnings.
              (function(foo) {
                  return 5;
              })();
              
              // Unused recursive functions also cause warnings.
              function fact(n) {
                  if (n < 2) return 1;
                  return n * fact(n - 1);
              }
              
              // When a function definition destructures an array, unused entries from the array also cause warnings.
              function getY([x, y]) {
                  return y;
              }

              Examples of correct code for this rule:

              /*eslint no-unused-vars: "error"*/
              
              var x = 10;
              alert(x);
              
              // foo is considered used here
              myFunc(function foo() {
                  // ...
              }.bind(this));
              
              (function(foo) {
                  return foo;
              })();
              
              var myFunc;
              myFunc = setTimeout(function() {
                  // myFunc is considered used
                  myFunc();
              }, 50);
              
              // Only the second argument from the descructured array is used.
              function getY([, y]) {
                  return y;
              }

              exported

              In environments outside of CommonJS or ECMAScript modules, you may use var to create a global variable that may be used by other scripts. You can use the /* exported variableName */ comment block to indicate that this variable is being exported and therefore should not be considered unused.

              Note that /* exported */ has no effect for any of the following:

              • when the environment is node or commonjs
              • when parserOptions.sourceType is module
              • when ecmaFeatures.globalReturn is true

              The line comment // exported variableName will not work as exported is not line-specific.

              Examples of correct code for /* exported variableName */ operation:

              /* exported global_var */
              
              var global_var = 42;

              Options

              This rule takes one argument which can be a string or an object. The string settings are the same as those of the vars property (explained below).

              By default this rule is enabled with all option for variables and after-used for arguments.

              {
                  "rules": {
                      "no-unused-vars": ["error", { "vars": "all", "args": "after-used", "ignoreRestSiblings": false }]
                  }
              }

              vars

              The vars option has two settings:

              • all checks all variables for usage, including those in the global scope. This is the default setting.
              • local checks only that locally-declared variables are used but will allow global variables to be unused.

              vars: local

              Examples of correct code for the { "vars": "local" } option:

              /*eslint no-unused-vars: ["error", { "vars": "local" }]*/
              /*global some_unused_var */
              
              some_unused_var = 42;

              varsIgnorePattern

              The varsIgnorePattern option specifies exceptions not to check for usage: variables whose names match a regexp pattern. For example, variables whose names contain ignored or Ignored.

              Examples of correct code for the { "varsIgnorePattern": "[iI]gnored" } option:

              /*eslint no-unused-vars: ["error", { "varsIgnorePattern": "[iI]gnored" }]*/
              
              var firstVarIgnored = 1;
              var secondVar = 2;
              console.log(secondVar);

              args

              The args option has three settings:

              • after-used - only the last argument must be used. This allows you, for instance, to have two named parameters to a function and as long as you use the second argument, ESLint will not warn you about the first. This is the default setting.
              • all - all named arguments must be used.
              • none - do not check arguments.

              args: after-used

              Examples of incorrect code for the default { "args": "after-used" } option:

              /*eslint no-unused-vars: ["error", { "args": "after-used" }]*/
              
              // 1 error
              // "baz" is defined but never used
              (function(foo, bar, baz) {
                  return bar;
              })();

              Examples of correct code for the default { "args": "after-used" } option:

              /*eslint no-unused-vars: ["error", {"args": "after-used"}]*/
              
              (function(foo, bar, baz) {
                  return baz;
              })();

              args: all

              Examples of incorrect code for the { "args": "all" } option:

              /*eslint no-unused-vars: ["error", { "args": "all" }]*/
              
              // 2 errors
              // "foo" is defined but never used
              // "baz" is defined but never used
              (function(foo, bar, baz) {
                  return bar;
              })();

              args: none

              Examples of correct code for the { "args": "none" } option:

              /*eslint no-unused-vars: ["error", { "args": "none" }]*/
              
              (function(foo, bar, baz) {
                  return bar;
              })();

              ignoreRestSiblings

              The ignoreRestSiblings option is a boolean (default: false). Using a Rest Property it is possible to "omit" properties from an object, but by default the sibling properties are marked as "unused". With this option enabled the rest property's siblings are ignored.

              Examples of correct code for the { "ignoreRestSiblings": true } option:

              /*eslint no-unused-vars: ["error", { "ignoreRestSiblings": true }]*/
              // 'type' is ignored because it has a rest property sibling.
              var { type, ...coords } = data;

              argsIgnorePattern

              The argsIgnorePattern option specifies exceptions not to check for usage: arguments whose names match a regexp pattern. For example, variables whose names begin with an underscore.

              Examples of correct code for the { "argsIgnorePattern": "^_" } option:

              /*eslint no-unused-vars: ["error", { "argsIgnorePattern": "^_" }]*/
              
              function foo(x, _y) {
                  return x + 1;
              }
              foo();

              caughtErrors

              The caughtErrors option is used for catch block arguments validation.

              It has two settings:

              • none - do not check error objects. This is the default setting.
              • all - all named arguments must be used.

              caughtErrors: none

              Not specifying this rule is equivalent of assigning it to none.

              Examples of correct code for the { "caughtErrors": "none" } option:

              /*eslint no-unused-vars: ["error", { "caughtErrors": "none" }]*/
              
              try {
                  //...
              } catch (err) {
                  console.error("errors");
              }

              caughtErrors: all

              Examples of incorrect code for the { "caughtErrors": "all" } option:

              /*eslint no-unused-vars: ["error", { "caughtErrors": "all" }]*/
              
              // 1 error
              // "err" is defined but never used
              try {
                  //...
              } catch (err) {
                  console.error("errors");
              }

              caughtErrorsIgnorePattern

              The caughtErrorsIgnorePattern option specifies exceptions not to check for usage: catch arguments whose names match a regexp pattern. For example, variables whose names begin with a string 'ignore'.

              Examples of correct code for the { "caughtErrorsIgnorePattern": "^ignore" } option:

              /*eslint no-unused-vars: ["error", { "caughtErrorsIgnorePattern": "^ignore" }]*/
              
              try {
                  //...
              } catch (ignoreErr) {
                  console.error("errors");
              }

              When Not To Use It

              If you don't want to be notified about unused variables or function arguments, you can safely turn this rule off. Source: http://eslint.org/docs/rules/

              'it' is defined but never used.
              Open

              declare var it: {
              Severity: Minor
              Found in flow-typed/npm/jest_v20.x.x.js by eslint

              Disallow Unused Variables (no-unused-vars)

              Variables that are declared and not used anywhere in the code are most likely an error due to incomplete refactoring. Such variables take up space in the code and can lead to confusion by readers.

              Rule Details

              This rule is aimed at eliminating unused variables, functions, and parameters of functions.

              A variable is considered to be used if any of the following are true:

              • It represents a function that is called (doSomething())
              • It is read (var y = x)
              • It is passed into a function as an argument (doSomething(x))
              • It is read inside of a function that is passed to another function (doSomething(function() { foo(); }))

              A variable is not considered to be used if it is only ever assigned to (var x = 5) or declared.

              Examples of incorrect code for this rule:

              /*eslint no-unused-vars: "error"*/
              /*global some_unused_var*/
              
              // It checks variables you have defined as global
              some_unused_var = 42;
              
              var x;
              
              // Write-only variables are not considered as used.
              var y = 10;
              y = 5;
              
              // A read for a modification of itself is not considered as used.
              var z = 0;
              z = z + 1;
              
              // By default, unused arguments cause warnings.
              (function(foo) {
                  return 5;
              })();
              
              // Unused recursive functions also cause warnings.
              function fact(n) {
                  if (n < 2) return 1;
                  return n * fact(n - 1);
              }
              
              // When a function definition destructures an array, unused entries from the array also cause warnings.
              function getY([x, y]) {
                  return y;
              }

              Examples of correct code for this rule:

              /*eslint no-unused-vars: "error"*/
              
              var x = 10;
              alert(x);
              
              // foo is considered used here
              myFunc(function foo() {
                  // ...
              }.bind(this));
              
              (function(foo) {
                  return foo;
              })();
              
              var myFunc;
              myFunc = setTimeout(function() {
                  // myFunc is considered used
                  myFunc();
              }, 50);
              
              // Only the second argument from the descructured array is used.
              function getY([, y]) {
                  return y;
              }

              exported

              In environments outside of CommonJS or ECMAScript modules, you may use var to create a global variable that may be used by other scripts. You can use the /* exported variableName */ comment block to indicate that this variable is being exported and therefore should not be considered unused.

              Note that /* exported */ has no effect for any of the following:

              • when the environment is node or commonjs
              • when parserOptions.sourceType is module
              • when ecmaFeatures.globalReturn is true

              The line comment // exported variableName will not work as exported is not line-specific.

              Examples of correct code for /* exported variableName */ operation:

              /* exported global_var */
              
              var global_var = 42;

              Options

              This rule takes one argument which can be a string or an object. The string settings are the same as those of the vars property (explained below).

              By default this rule is enabled with all option for variables and after-used for arguments.

              {
                  "rules": {
                      "no-unused-vars": ["error", { "vars": "all", "args": "after-used", "ignoreRestSiblings": false }]
                  }
              }

              vars

              The vars option has two settings:

              • all checks all variables for usage, including those in the global scope. This is the default setting.
              • local checks only that locally-declared variables are used but will allow global variables to be unused.

              vars: local

              Examples of correct code for the { "vars": "local" } option:

              /*eslint no-unused-vars: ["error", { "vars": "local" }]*/
              /*global some_unused_var */
              
              some_unused_var = 42;

              varsIgnorePattern

              The varsIgnorePattern option specifies exceptions not to check for usage: variables whose names match a regexp pattern. For example, variables whose names contain ignored or Ignored.

              Examples of correct code for the { "varsIgnorePattern": "[iI]gnored" } option:

              /*eslint no-unused-vars: ["error", { "varsIgnorePattern": "[iI]gnored" }]*/
              
              var firstVarIgnored = 1;
              var secondVar = 2;
              console.log(secondVar);

              args

              The args option has three settings:

              • after-used - only the last argument must be used. This allows you, for instance, to have two named parameters to a function and as long as you use the second argument, ESLint will not warn you about the first. This is the default setting.
              • all - all named arguments must be used.
              • none - do not check arguments.

              args: after-used

              Examples of incorrect code for the default { "args": "after-used" } option:

              /*eslint no-unused-vars: ["error", { "args": "after-used" }]*/
              
              // 1 error
              // "baz" is defined but never used
              (function(foo, bar, baz) {
                  return bar;
              })();

              Examples of correct code for the default { "args": "after-used" } option:

              /*eslint no-unused-vars: ["error", {"args": "after-used"}]*/
              
              (function(foo, bar, baz) {
                  return baz;
              })();

              args: all

              Examples of incorrect code for the { "args": "all" } option:

              /*eslint no-unused-vars: ["error", { "args": "all" }]*/
              
              // 2 errors
              // "foo" is defined but never used
              // "baz" is defined but never used
              (function(foo, bar, baz) {
                  return bar;
              })();

              args: none

              Examples of correct code for the { "args": "none" } option:

              /*eslint no-unused-vars: ["error", { "args": "none" }]*/
              
              (function(foo, bar, baz) {
                  return bar;
              })();

              ignoreRestSiblings

              The ignoreRestSiblings option is a boolean (default: false). Using a Rest Property it is possible to "omit" properties from an object, but by default the sibling properties are marked as "unused". With this option enabled the rest property's siblings are ignored.

              Examples of correct code for the { "ignoreRestSiblings": true } option:

              /*eslint no-unused-vars: ["error", { "ignoreRestSiblings": true }]*/
              // 'type' is ignored because it has a rest property sibling.
              var { type, ...coords } = data;

              argsIgnorePattern

              The argsIgnorePattern option specifies exceptions not to check for usage: arguments whose names match a regexp pattern. For example, variables whose names begin with an underscore.

              Examples of correct code for the { "argsIgnorePattern": "^_" } option:

              /*eslint no-unused-vars: ["error", { "argsIgnorePattern": "^_" }]*/
              
              function foo(x, _y) {
                  return x + 1;
              }
              foo();

              caughtErrors

              The caughtErrors option is used for catch block arguments validation.

              It has two settings:

              • none - do not check error objects. This is the default setting.
              • all - all named arguments must be used.

              caughtErrors: none

              Not specifying this rule is equivalent of assigning it to none.

              Examples of correct code for the { "caughtErrors": "none" } option:

              /*eslint no-unused-vars: ["error", { "caughtErrors": "none" }]*/
              
              try {
                  //...
              } catch (err) {
                  console.error("errors");
              }

              caughtErrors: all

              Examples of incorrect code for the { "caughtErrors": "all" } option:

              /*eslint no-unused-vars: ["error", { "caughtErrors": "all" }]*/
              
              // 1 error
              // "err" is defined but never used
              try {
                  //...
              } catch (err) {
                  console.error("errors");
              }

              caughtErrorsIgnorePattern

              The caughtErrorsIgnorePattern option specifies exceptions not to check for usage: catch arguments whose names match a regexp pattern. For example, variables whose names begin with a string 'ignore'.

              Examples of correct code for the { "caughtErrorsIgnorePattern": "^ignore" } option:

              /*eslint no-unused-vars: ["error", { "caughtErrorsIgnorePattern": "^ignore" }]*/
              
              try {
                  //...
              } catch (ignoreErr) {
                  console.error("errors");
              }

              When Not To Use It

              If you don't want to be notified about unused variables or function arguments, you can safely turn this rule off. Source: http://eslint.org/docs/rules/

              'xdescribe' is defined but never used.
              Open

              declare var xdescribe: typeof describe;
              Severity: Minor
              Found in flow-typed/npm/jest_v20.x.x.js by eslint

              Disallow Unused Variables (no-unused-vars)

              Variables that are declared and not used anywhere in the code are most likely an error due to incomplete refactoring. Such variables take up space in the code and can lead to confusion by readers.

              Rule Details

              This rule is aimed at eliminating unused variables, functions, and parameters of functions.

              A variable is considered to be used if any of the following are true:

              • It represents a function that is called (doSomething())
              • It is read (var y = x)
              • It is passed into a function as an argument (doSomething(x))
              • It is read inside of a function that is passed to another function (doSomething(function() { foo(); }))

              A variable is not considered to be used if it is only ever assigned to (var x = 5) or declared.

              Examples of incorrect code for this rule:

              /*eslint no-unused-vars: "error"*/
              /*global some_unused_var*/
              
              // It checks variables you have defined as global
              some_unused_var = 42;
              
              var x;
              
              // Write-only variables are not considered as used.
              var y = 10;
              y = 5;
              
              // A read for a modification of itself is not considered as used.
              var z = 0;
              z = z + 1;
              
              // By default, unused arguments cause warnings.
              (function(foo) {
                  return 5;
              })();
              
              // Unused recursive functions also cause warnings.
              function fact(n) {
                  if (n < 2) return 1;
                  return n * fact(n - 1);
              }
              
              // When a function definition destructures an array, unused entries from the array also cause warnings.
              function getY([x, y]) {
                  return y;
              }

              Examples of correct code for this rule:

              /*eslint no-unused-vars: "error"*/
              
              var x = 10;
              alert(x);
              
              // foo is considered used here
              myFunc(function foo() {
                  // ...
              }.bind(this));
              
              (function(foo) {
                  return foo;
              })();
              
              var myFunc;
              myFunc = setTimeout(function() {
                  // myFunc is considered used
                  myFunc();
              }, 50);
              
              // Only the second argument from the descructured array is used.
              function getY([, y]) {
                  return y;
              }

              exported

              In environments outside of CommonJS or ECMAScript modules, you may use var to create a global variable that may be used by other scripts. You can use the /* exported variableName */ comment block to indicate that this variable is being exported and therefore should not be considered unused.

              Note that /* exported */ has no effect for any of the following:

              • when the environment is node or commonjs
              • when parserOptions.sourceType is module
              • when ecmaFeatures.globalReturn is true

              The line comment // exported variableName will not work as exported is not line-specific.

              Examples of correct code for /* exported variableName */ operation:

              /* exported global_var */
              
              var global_var = 42;

              Options

              This rule takes one argument which can be a string or an object. The string settings are the same as those of the vars property (explained below).

              By default this rule is enabled with all option for variables and after-used for arguments.

              {
                  "rules": {
                      "no-unused-vars": ["error", { "vars": "all", "args": "after-used", "ignoreRestSiblings": false }]
                  }
              }

              vars

              The vars option has two settings:

              • all checks all variables for usage, including those in the global scope. This is the default setting.
              • local checks only that locally-declared variables are used but will allow global variables to be unused.

              vars: local

              Examples of correct code for the { "vars": "local" } option:

              /*eslint no-unused-vars: ["error", { "vars": "local" }]*/
              /*global some_unused_var */
              
              some_unused_var = 42;

              varsIgnorePattern

              The varsIgnorePattern option specifies exceptions not to check for usage: variables whose names match a regexp pattern. For example, variables whose names contain ignored or Ignored.

              Examples of correct code for the { "varsIgnorePattern": "[iI]gnored" } option:

              /*eslint no-unused-vars: ["error", { "varsIgnorePattern": "[iI]gnored" }]*/
              
              var firstVarIgnored = 1;
              var secondVar = 2;
              console.log(secondVar);

              args

              The args option has three settings:

              • after-used - only the last argument must be used. This allows you, for instance, to have two named parameters to a function and as long as you use the second argument, ESLint will not warn you about the first. This is the default setting.
              • all - all named arguments must be used.
              • none - do not check arguments.

              args: after-used

              Examples of incorrect code for the default { "args": "after-used" } option:

              /*eslint no-unused-vars: ["error", { "args": "after-used" }]*/
              
              // 1 error
              // "baz" is defined but never used
              (function(foo, bar, baz) {
                  return bar;
              })();

              Examples of correct code for the default { "args": "after-used" } option:

              /*eslint no-unused-vars: ["error", {"args": "after-used"}]*/
              
              (function(foo, bar, baz) {
                  return baz;
              })();

              args: all

              Examples of incorrect code for the { "args": "all" } option:

              /*eslint no-unused-vars: ["error", { "args": "all" }]*/
              
              // 2 errors
              // "foo" is defined but never used
              // "baz" is defined but never used
              (function(foo, bar, baz) {
                  return bar;
              })();

              args: none

              Examples of correct code for the { "args": "none" } option:

              /*eslint no-unused-vars: ["error", { "args": "none" }]*/
              
              (function(foo, bar, baz) {
                  return bar;
              })();

              ignoreRestSiblings

              The ignoreRestSiblings option is a boolean (default: false). Using a Rest Property it is possible to "omit" properties from an object, but by default the sibling properties are marked as "unused". With this option enabled the rest property's siblings are ignored.

              Examples of correct code for the { "ignoreRestSiblings": true } option:

              /*eslint no-unused-vars: ["error", { "ignoreRestSiblings": true }]*/
              // 'type' is ignored because it has a rest property sibling.
              var { type, ...coords } = data;

              argsIgnorePattern

              The argsIgnorePattern option specifies exceptions not to check for usage: arguments whose names match a regexp pattern. For example, variables whose names begin with an underscore.

              Examples of correct code for the { "argsIgnorePattern": "^_" } option:

              /*eslint no-unused-vars: ["error", { "argsIgnorePattern": "^_" }]*/
              
              function foo(x, _y) {
                  return x + 1;
              }
              foo();

              caughtErrors

              The caughtErrors option is used for catch block arguments validation.

              It has two settings:

              • none - do not check error objects. This is the default setting.
              • all - all named arguments must be used.

              caughtErrors: none

              Not specifying this rule is equivalent of assigning it to none.

              Examples of correct code for the { "caughtErrors": "none" } option:

              /*eslint no-unused-vars: ["error", { "caughtErrors": "none" }]*/
              
              try {
                  //...
              } catch (err) {
                  console.error("errors");
              }

              caughtErrors: all

              Examples of incorrect code for the { "caughtErrors": "all" } option:

              /*eslint no-unused-vars: ["error", { "caughtErrors": "all" }]*/
              
              // 1 error
              // "err" is defined but never used
              try {
                  //...
              } catch (err) {
                  console.error("errors");
              }

              caughtErrorsIgnorePattern

              The caughtErrorsIgnorePattern option specifies exceptions not to check for usage: catch arguments whose names match a regexp pattern. For example, variables whose names begin with a string 'ignore'.

              Examples of correct code for the { "caughtErrorsIgnorePattern": "^ignore" } option:

              /*eslint no-unused-vars: ["error", { "caughtErrorsIgnorePattern": "^ignore" }]*/
              
              try {
                  //...
              } catch (ignoreErr) {
                  console.error("errors");
              }

              When Not To Use It

              If you don't want to be notified about unused variables or function arguments, you can safely turn this rule off. Source: http://eslint.org/docs/rules/

              propType "options" is not required, but has no corresponding defaultProp declaration.
              Open

                options?: {
              Severity: Minor
              Found in src/index.js by eslint

              For more information visit Source: http://eslint.org/docs/rules/

              Severity
              Category
              Status
              Source
              Language