i18next/react-i18next

View on GitHub

Showing 42 of 42 total issues

Avoid too many return statements within this function.
Open

  return false;
Severity: Major
Found in src/utils.js - About 30 mins to fix

    Avoid too many return statements within this function.
    Open

      if (!i18n.services.backendConnector.backend) return true;
    Severity: Major
    Found in src/utils.js - About 30 mins to fix

      Definition for rule 'jsx-a11y/anchor-is-valid' was not found
      Open

      import { useState, useEffect, useContext, useRef } from 'react';
      Severity: Minor
      Found in src/useTranslation.js by eslint

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

      Definition for rule 'jsx-a11y/anchor-is-valid' was not found
      Open

      import React, { useContext } from 'react';
      Severity: Minor
      Found in src/Trans.js by eslint

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

      Assignment to function parameter 'mem'.
      Open

            mem += `<${componentFoundIndex}>${mergeChildren(
      Severity: Minor
      Found in icu.macro.js by eslint

      Disallow Reassignment of Function Parameters (no-param-reassign)

      Assignment to variables declared as function parameters can be misleading and lead to confusing behavior, as modifying function parameters will also mutate the arguments object. Often, assignment to function parameters is unintended and indicative of a mistake or programmer error.

      This rule can be also configured to fail when function parameters are modified. Side effects on parameters can cause counter-intuitive execution flow and make errors difficult to track down.

      Rule Details

      This rule aims to prevent unintended behavior caused by modification or reassignment of function parameters.

      Examples of incorrect code for this rule:

      /*eslint no-param-reassign: "error"*/
      
      function foo(bar) {
          bar = 13;
      }
      
      function foo(bar) {
          bar++;
      }

      Examples of correct code for this rule:

      /*eslint no-param-reassign: "error"*/
      
      function foo(bar) {
          var baz = bar;
      }

      Options

      This rule takes one option, an object, with a boolean property "props" and an array "ignorePropertyModificationsFor". "props" is false by default. If "props" is set to true, this rule warns against the modification of parameter properties unless they're included in "ignorePropertyModificationsFor", which is an empty array by default.

      props

      Examples of correct code for the default { "props": false } option:

      /*eslint no-param-reassign: ["error", { "props": false }]*/
      
      function foo(bar) {
          bar.prop = "value";
      }
      
      function foo(bar) {
          delete bar.aaa;
      }
      
      function foo(bar) {
          bar.aaa++;
      }

      Examples of incorrect code for the { "props": true } option:

      /*eslint no-param-reassign: ["error", { "props": true }]*/
      
      function foo(bar) {
          bar.prop = "value";
      }
      
      function foo(bar) {
          delete bar.aaa;
      }
      
      function foo(bar) {
          bar.aaa++;
      }

      Examples of correct code for the { "props": true } option with "ignorePropertyModificationsFor" set:

      /*eslint no-param-reassign: ["error", { "props": true, "ignorePropertyModificationsFor": ["bar"] }]*/
      
      function foo(bar) {
          bar.prop = "value";
      }
      
      function foo(bar) {
          delete bar.aaa;
      }
      
      function foo(bar) {
          bar.aaa++;
      }

      When Not To Use It

      If you want to allow assignment to function parameters, then you can safely disable this rule.

      Further Reading

      Definition for rule 'jsx-a11y/anchor-is-valid' was not found
      Open

      import React from 'react';
      Severity: Minor
      Found in src/context.js by eslint

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

      't' is assigned a value but never used.
      Open

        const t = babel.types;
      Severity: Minor
      Found in icu.macro.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/

      Assignment to function parameter 'mem'.
      Open

            mem += `{${ele.expression.expressions
      Severity: Minor
      Found in icu.macro.js by eslint

      Disallow Reassignment of Function Parameters (no-param-reassign)

      Assignment to variables declared as function parameters can be misleading and lead to confusing behavior, as modifying function parameters will also mutate the arguments object. Often, assignment to function parameters is unintended and indicative of a mistake or programmer error.

      This rule can be also configured to fail when function parameters are modified. Side effects on parameters can cause counter-intuitive execution flow and make errors difficult to track down.

      Rule Details

      This rule aims to prevent unintended behavior caused by modification or reassignment of function parameters.

      Examples of incorrect code for this rule:

      /*eslint no-param-reassign: "error"*/
      
      function foo(bar) {
          bar = 13;
      }
      
      function foo(bar) {
          bar++;
      }

      Examples of correct code for this rule:

      /*eslint no-param-reassign: "error"*/
      
      function foo(bar) {
          var baz = bar;
      }

      Options

      This rule takes one option, an object, with a boolean property "props" and an array "ignorePropertyModificationsFor". "props" is false by default. If "props" is set to true, this rule warns against the modification of parameter properties unless they're included in "ignorePropertyModificationsFor", which is an empty array by default.

      props

      Examples of correct code for the default { "props": false } option:

      /*eslint no-param-reassign: ["error", { "props": false }]*/
      
      function foo(bar) {
          bar.prop = "value";
      }
      
      function foo(bar) {
          delete bar.aaa;
      }
      
      function foo(bar) {
          bar.aaa++;
      }

      Examples of incorrect code for the { "props": true } option:

      /*eslint no-param-reassign: ["error", { "props": true }]*/
      
      function foo(bar) {
          bar.prop = "value";
      }
      
      function foo(bar) {
          delete bar.aaa;
      }
      
      function foo(bar) {
          bar.aaa++;
      }

      Examples of correct code for the { "props": true } option with "ignorePropertyModificationsFor" set:

      /*eslint no-param-reassign: ["error", { "props": true, "ignorePropertyModificationsFor": ["bar"] }]*/
      
      function foo(bar) {
          bar.prop = "value";
      }
      
      function foo(bar) {
          delete bar.aaa;
      }
      
      function foo(bar) {
          bar.aaa++;
      }

      When Not To Use It

      If you want to allow assignment to function parameters, then you can safely disable this rule.

      Further Reading

      Unary operator '++' used.
      Open

            componentFoundIndex++;
      Severity: Minor
      Found in icu.macro.js by eslint

      disallow the unary operators ++ and -- (no-plusplus)

      Because the unary ++ and -- operators are subject to automatic semicolon insertion, differences in whitespace can change semantics of source code.

      var i = 10;
      var j = 20;
      
      i ++
      j
      // i = 11, j = 20
      var i = 10;
      var j = 20;
      
      i
      ++
      j
      // i = 10, j = 21

      Rule Details

      This rule disallows the unary operators ++ and --.

      Examples of incorrect code for this rule:

      /*eslint no-plusplus: "error"*/
      
      var foo = 0;
      foo++;
      
      var bar = 42;
      bar--;
      
      for (i = 0; i < l; i++) {
          return;
      }

      Examples of correct code for this rule:

      /*eslint no-plusplus: "error"*/
      
      var foo = 0;
      foo += 1;
      
      var bar = 42;
      bar -= 1;
      
      for (i = 0; i < l; i += 1) {
          return;
      }

      Options

      This rule has an object option.

      • "allowForLoopAfterthoughts": true allows unary operators ++ and -- in the afterthought (final expression) of a for loop.

      allowForLoopAfterthoughts

      Examples of correct code for this rule with the { "allowForLoopAfterthoughts": true } option:

      /*eslint no-plusplus: ["error", { "allowForLoopAfterthoughts": true }]*/
      
      for (i = 0; i < l; i++) {
          return;
      }
      
      for (i = 0; i < l; i--) {
          return;
      }

      Source: http://eslint.org/docs/rules/

      Assignment to function parameter 'mem'.
      Open

          if (ele.expression && ele.expression.properties) mem = mem.concat(ele.expression.properties);
      Severity: Minor
      Found in icu.macro.js by eslint

      Disallow Reassignment of Function Parameters (no-param-reassign)

      Assignment to variables declared as function parameters can be misleading and lead to confusing behavior, as modifying function parameters will also mutate the arguments object. Often, assignment to function parameters is unintended and indicative of a mistake or programmer error.

      This rule can be also configured to fail when function parameters are modified. Side effects on parameters can cause counter-intuitive execution flow and make errors difficult to track down.

      Rule Details

      This rule aims to prevent unintended behavior caused by modification or reassignment of function parameters.

      Examples of incorrect code for this rule:

      /*eslint no-param-reassign: "error"*/
      
      function foo(bar) {
          bar = 13;
      }
      
      function foo(bar) {
          bar++;
      }

      Examples of correct code for this rule:

      /*eslint no-param-reassign: "error"*/
      
      function foo(bar) {
          var baz = bar;
      }

      Options

      This rule takes one option, an object, with a boolean property "props" and an array "ignorePropertyModificationsFor". "props" is false by default. If "props" is set to true, this rule warns against the modification of parameter properties unless they're included in "ignorePropertyModificationsFor", which is an empty array by default.

      props

      Examples of correct code for the default { "props": false } option:

      /*eslint no-param-reassign: ["error", { "props": false }]*/
      
      function foo(bar) {
          bar.prop = "value";
      }
      
      function foo(bar) {
          delete bar.aaa;
      }
      
      function foo(bar) {
          bar.aaa++;
      }

      Examples of incorrect code for the { "props": true } option:

      /*eslint no-param-reassign: ["error", { "props": true }]*/
      
      function foo(bar) {
          bar.prop = "value";
      }
      
      function foo(bar) {
          delete bar.aaa;
      }
      
      function foo(bar) {
          bar.aaa++;
      }

      Examples of correct code for the { "props": true } option with "ignorePropertyModificationsFor" set:

      /*eslint no-param-reassign: ["error", { "props": true, "ignorePropertyModificationsFor": ["bar"] }]*/
      
      function foo(bar) {
          bar.prop = "value";
      }
      
      function foo(bar) {
          delete bar.aaa;
      }
      
      function foo(bar) {
          bar.aaa++;
      }

      When Not To Use It

      If you want to allow assignment to function parameters, then you can safely disable this rule.

      Further Reading

      Assignment to function parameter 'mem'.
      Open

            mem = mem.concat(getValues(ele.children, babel));
      Severity: Minor
      Found in icu.macro.js by eslint

      Disallow Reassignment of Function Parameters (no-param-reassign)

      Assignment to variables declared as function parameters can be misleading and lead to confusing behavior, as modifying function parameters will also mutate the arguments object. Often, assignment to function parameters is unintended and indicative of a mistake or programmer error.

      This rule can be also configured to fail when function parameters are modified. Side effects on parameters can cause counter-intuitive execution flow and make errors difficult to track down.

      Rule Details

      This rule aims to prevent unintended behavior caused by modification or reassignment of function parameters.

      Examples of incorrect code for this rule:

      /*eslint no-param-reassign: "error"*/
      
      function foo(bar) {
          bar = 13;
      }
      
      function foo(bar) {
          bar++;
      }

      Examples of correct code for this rule:

      /*eslint no-param-reassign: "error"*/
      
      function foo(bar) {
          var baz = bar;
      }

      Options

      This rule takes one option, an object, with a boolean property "props" and an array "ignorePropertyModificationsFor". "props" is false by default. If "props" is set to true, this rule warns against the modification of parameter properties unless they're included in "ignorePropertyModificationsFor", which is an empty array by default.

      props

      Examples of correct code for the default { "props": false } option:

      /*eslint no-param-reassign: ["error", { "props": false }]*/
      
      function foo(bar) {
          bar.prop = "value";
      }
      
      function foo(bar) {
          delete bar.aaa;
      }
      
      function foo(bar) {
          bar.aaa++;
      }

      Examples of incorrect code for the { "props": true } option:

      /*eslint no-param-reassign: ["error", { "props": true }]*/
      
      function foo(bar) {
          bar.prop = "value";
      }
      
      function foo(bar) {
          delete bar.aaa;
      }
      
      function foo(bar) {
          bar.aaa++;
      }

      Examples of correct code for the { "props": true } option with "ignorePropertyModificationsFor" set:

      /*eslint no-param-reassign: ["error", { "props": true, "ignorePropertyModificationsFor": ["bar"] }]*/
      
      function foo(bar) {
          bar.prop = "value";
      }
      
      function foo(bar) {
          delete bar.aaa;
      }
      
      function foo(bar) {
          bar.aaa++;
      }

      When Not To Use It

      If you want to allow assignment to function parameters, then you can safely disable this rule.

      Further Reading

      Definition for rule 'jsx-a11y/anchor-is-valid' was not found
      Open

      const { createMacro } = require('babel-plugin-macros');
      Severity: Minor
      Found in icu.macro.js by eslint

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

      Definition for rule 'jsx-a11y/anchor-is-valid' was not found
      Open

      import { createElement } from 'react';
      Severity: Minor
      Found in src/I18nextProvider.js by eslint

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

      Assignment to function parameter 'mem'.
      Open

          if (ele.expression && ele.expression.value) mem += ele.expression.value;
      Severity: Minor
      Found in icu.macro.js by eslint

      Disallow Reassignment of Function Parameters (no-param-reassign)

      Assignment to variables declared as function parameters can be misleading and lead to confusing behavior, as modifying function parameters will also mutate the arguments object. Often, assignment to function parameters is unintended and indicative of a mistake or programmer error.

      This rule can be also configured to fail when function parameters are modified. Side effects on parameters can cause counter-intuitive execution flow and make errors difficult to track down.

      Rule Details

      This rule aims to prevent unintended behavior caused by modification or reassignment of function parameters.

      Examples of incorrect code for this rule:

      /*eslint no-param-reassign: "error"*/
      
      function foo(bar) {
          bar = 13;
      }
      
      function foo(bar) {
          bar++;
      }

      Examples of correct code for this rule:

      /*eslint no-param-reassign: "error"*/
      
      function foo(bar) {
          var baz = bar;
      }

      Options

      This rule takes one option, an object, with a boolean property "props" and an array "ignorePropertyModificationsFor". "props" is false by default. If "props" is set to true, this rule warns against the modification of parameter properties unless they're included in "ignorePropertyModificationsFor", which is an empty array by default.

      props

      Examples of correct code for the default { "props": false } option:

      /*eslint no-param-reassign: ["error", { "props": false }]*/
      
      function foo(bar) {
          bar.prop = "value";
      }
      
      function foo(bar) {
          delete bar.aaa;
      }
      
      function foo(bar) {
          bar.aaa++;
      }

      Examples of incorrect code for the { "props": true } option:

      /*eslint no-param-reassign: ["error", { "props": true }]*/
      
      function foo(bar) {
          bar.prop = "value";
      }
      
      function foo(bar) {
          delete bar.aaa;
      }
      
      function foo(bar) {
          bar.aaa++;
      }

      Examples of correct code for the { "props": true } option with "ignorePropertyModificationsFor" set:

      /*eslint no-param-reassign: ["error", { "props": true, "ignorePropertyModificationsFor": ["bar"] }]*/
      
      function foo(bar) {
          bar.prop = "value";
      }
      
      function foo(bar) {
          delete bar.aaa;
      }
      
      function foo(bar) {
          bar.aaa++;
      }

      When Not To Use It

      If you want to allow assignment to function parameters, then you can safely disable this rule.

      Further Reading

      Definition for rule 'jsx-a11y/anchor-is-valid' was not found
      Open

      import { useContext } from 'react';
      Severity: Minor
      Found in src/useSSR.js by eslint

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

      Definition for rule 'jsx-a11y/anchor-is-valid' was not found
      Open

      import { useTranslation } from './useTranslation';
      Severity: Minor
      Found in src/Translation.js by eslint

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

      Definition for rule 'jsx-a11y/anchor-is-valid' was not found
      Open

      import React from 'react';
      Severity: Minor
      Found in src/withTranslation.js by eslint

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

      Assignment to function parameter 'mem'.
      Open

          if (t.isJSXText(ele) && ele.value) mem += trimIndent(ele.value);
      Severity: Minor
      Found in icu.macro.js by eslint

      Disallow Reassignment of Function Parameters (no-param-reassign)

      Assignment to variables declared as function parameters can be misleading and lead to confusing behavior, as modifying function parameters will also mutate the arguments object. Often, assignment to function parameters is unintended and indicative of a mistake or programmer error.

      This rule can be also configured to fail when function parameters are modified. Side effects on parameters can cause counter-intuitive execution flow and make errors difficult to track down.

      Rule Details

      This rule aims to prevent unintended behavior caused by modification or reassignment of function parameters.

      Examples of incorrect code for this rule:

      /*eslint no-param-reassign: "error"*/
      
      function foo(bar) {
          bar = 13;
      }
      
      function foo(bar) {
          bar++;
      }

      Examples of correct code for this rule:

      /*eslint no-param-reassign: "error"*/
      
      function foo(bar) {
          var baz = bar;
      }

      Options

      This rule takes one option, an object, with a boolean property "props" and an array "ignorePropertyModificationsFor". "props" is false by default. If "props" is set to true, this rule warns against the modification of parameter properties unless they're included in "ignorePropertyModificationsFor", which is an empty array by default.

      props

      Examples of correct code for the default { "props": false } option:

      /*eslint no-param-reassign: ["error", { "props": false }]*/
      
      function foo(bar) {
          bar.prop = "value";
      }
      
      function foo(bar) {
          delete bar.aaa;
      }
      
      function foo(bar) {
          bar.aaa++;
      }

      Examples of incorrect code for the { "props": true } option:

      /*eslint no-param-reassign: ["error", { "props": true }]*/
      
      function foo(bar) {
          bar.prop = "value";
      }
      
      function foo(bar) {
          delete bar.aaa;
      }
      
      function foo(bar) {
          bar.aaa++;
      }

      Examples of correct code for the { "props": true } option with "ignorePropertyModificationsFor" set:

      /*eslint no-param-reassign: ["error", { "props": true, "ignorePropertyModificationsFor": ["bar"] }]*/
      
      function foo(bar) {
          bar.prop = "value";
      }
      
      function foo(bar) {
          delete bar.aaa;
      }
      
      function foo(bar) {
          bar.aaa++;
      }

      When Not To Use It

      If you want to allow assignment to function parameters, then you can safely disable this rule.

      Further Reading

      Assignment to function parameter 'mem'.
      Open

          if (ele.expression && ele.expression.name) mem += `{${ele.expression.name}}`;
      Severity: Minor
      Found in icu.macro.js by eslint

      Disallow Reassignment of Function Parameters (no-param-reassign)

      Assignment to variables declared as function parameters can be misleading and lead to confusing behavior, as modifying function parameters will also mutate the arguments object. Often, assignment to function parameters is unintended and indicative of a mistake or programmer error.

      This rule can be also configured to fail when function parameters are modified. Side effects on parameters can cause counter-intuitive execution flow and make errors difficult to track down.

      Rule Details

      This rule aims to prevent unintended behavior caused by modification or reassignment of function parameters.

      Examples of incorrect code for this rule:

      /*eslint no-param-reassign: "error"*/
      
      function foo(bar) {
          bar = 13;
      }
      
      function foo(bar) {
          bar++;
      }

      Examples of correct code for this rule:

      /*eslint no-param-reassign: "error"*/
      
      function foo(bar) {
          var baz = bar;
      }

      Options

      This rule takes one option, an object, with a boolean property "props" and an array "ignorePropertyModificationsFor". "props" is false by default. If "props" is set to true, this rule warns against the modification of parameter properties unless they're included in "ignorePropertyModificationsFor", which is an empty array by default.

      props

      Examples of correct code for the default { "props": false } option:

      /*eslint no-param-reassign: ["error", { "props": false }]*/
      
      function foo(bar) {
          bar.prop = "value";
      }
      
      function foo(bar) {
          delete bar.aaa;
      }
      
      function foo(bar) {
          bar.aaa++;
      }

      Examples of incorrect code for the { "props": true } option:

      /*eslint no-param-reassign: ["error", { "props": true }]*/
      
      function foo(bar) {
          bar.prop = "value";
      }
      
      function foo(bar) {
          delete bar.aaa;
      }
      
      function foo(bar) {
          bar.aaa++;
      }

      Examples of correct code for the { "props": true } option with "ignorePropertyModificationsFor" set:

      /*eslint no-param-reassign: ["error", { "props": true, "ignorePropertyModificationsFor": ["bar"] }]*/
      
      function foo(bar) {
          bar.prop = "value";
      }
      
      function foo(bar) {
          delete bar.aaa;
      }
      
      function foo(bar) {
          bar.aaa++;
      }

      When Not To Use It

      If you want to allow assignment to function parameters, then you can safely disable this rule.

      Further Reading

      Definition for rule 'jsx-a11y/anchor-is-valid' was not found
      Open

      export function warn(...args) {
      Severity: Minor
      Found in src/utils.js by eslint

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

      Severity
      Category
      Status
      Source
      Language