i18next/react-i18next

View on GitHub

Showing 50 of 50 total issues

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

  Plural.forEach(referencePath => {
    if (referencePath.parentPath.type === 'JSXOpeningElement') {
      pluralAsJSX(
        referencePath.parentPath,
        {
Severity: Major
Found in icu.macro.js and 1 other location - About 2 hrs to fix
icu.macro.js on lines 31..44

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 100.

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

  Select.forEach(referencePath => {
    if (referencePath.parentPath.type === 'JSXOpeningElement') {
      selectAsJSX(
        referencePath.parentPath,
        {
Severity: Major
Found in icu.macro.js and 1 other location - About 2 hrs to fix
icu.macro.js on lines 15..28

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 100.

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

Function useTranslation has 49 lines of code (exceeds 25 allowed). Consider refactoring.
Open

export function useTranslation(ns, props = {}) {
  // assert we have the needed i18nInstance
  const { i18n: i18nFromProps } = props;
  const { i18n: i18nFromContext } = getHasUsedI18nextProvider() ? useContext(I18nContext) : {};
  const i18n = i18nFromProps || i18nFromContext || getI18n();
Severity: Minor
Found in src/useTranslation.js - About 1 hr to fix

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

          } else if (attr.node.name.name === 'switch') {
            // take the switch for plural element
            mem.values.push(toObjectProperty(attr.node.value.expression.name));
            mem.defaults = `{${attr.node.value.expression.name}, select, ${mem.defaults}`;
          } else if (attr.node.value.type === 'StringLiteral') {
    Severity: Major
    Found in icu.macro.js and 1 other location - About 1 hr to fix
    icu.macro.js on lines 75..97

    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 85.

    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

          } else if (attr.node.name.name === 'count') {
            // take the count for plural element
            mem.values.push(toObjectProperty(attr.node.value.expression.name));
            mem.defaults = `{${attr.node.value.expression.name}, plural, ${mem.defaults}`;
          } else if (attr.node.value.type === 'StringLiteral') {
    Severity: Major
    Found in icu.macro.js and 1 other location - About 1 hr to fix
    icu.macro.js on lines 119..136

    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 85.

    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

    Function renderNodes has 42 lines of code (exceeds 25 allowed). Consider refactoring.
    Open

    function renderNodes(children, targetString, i18n) {
      if (targetString === '') return [];
      if (!children) return [targetString];
    
      // v2 -> interpolates upfront no need for "some <0>{{var}}</0>"" -> will be just "some {{var}}" in translation file
    Severity: Minor
    Found in src/Trans.js - About 1 hr to fix

      Function useTranslation has a Cognitive Complexity of 13 (exceeds 5 allowed). Consider refactoring.
      Open

      export function useTranslation(ns, props = {}) {
        // assert we have the needed i18nInstance
        const { i18n: i18nFromProps } = props;
        const { i18n: i18nFromContext } = getHasUsedI18nextProvider() ? useContext(I18nContext) : {};
        const i18n = i18nFromProps || i18nFromContext || getI18n();
      Severity: Minor
      Found in src/useTranslation.js - About 1 hr to fix

      Cognitive Complexity

      Cognitive Complexity is a measure of how difficult a unit of code is to intuitively understand. Unlike Cyclomatic Complexity, which determines how difficult your code will be to test, Cognitive Complexity tells you how difficult your code will be to read and comprehend.

      A method's cognitive complexity is based on a few simple rules:

      • Code is not considered more complex when it uses shorthand that the language provides for collapsing multiple statements into one
      • Code is considered more complex for each "break in the linear flow of the code"
      • Code is considered more complex when "flow breaking structures are nested"

      Further reading

      Function nodesToString has 33 lines of code (exceeds 25 allowed). Consider refactoring.
      Open

      function nodesToString(mem, children, index) {
        if (!children) return '';
        if (Object.prototype.toString.call(children) !== '[object Array]') children = [children];
      
        children.forEach((child, i) => {
      Severity: Minor
      Found in src/Trans.js - About 1 hr to fix

        Function pluralAsJSX has a Cognitive Complexity of 11 (exceeds 5 allowed). Consider refactoring.
        Open

        function pluralAsJSX(parentPath, { attributes }, babel) {
          const t = babel.types;
          const toObjectProperty = (name, value) =>
            t.objectProperty(t.identifier(name), t.identifier(name), false, !value);
        
        
        Severity: Minor
        Found in icu.macro.js - About 1 hr to fix

        Cognitive Complexity

        Cognitive Complexity is a measure of how difficult a unit of code is to intuitively understand. Unlike Cyclomatic Complexity, which determines how difficult your code will be to test, Cognitive Complexity tells you how difficult your code will be to read and comprehend.

        A method's cognitive complexity is based on a few simple rules:

        • Code is not considered more complex when it uses shorthand that the language provides for collapsing multiple statements into one
        • Code is considered more complex for each "break in the linear flow of the code"
        • Code is considered more complex when "flow breaking structures are nested"

        Further reading

        Function Trans has a Cognitive Complexity of 10 (exceeds 5 allowed). Consider refactoring.
        Open

        export function Trans({
          children,
          count,
          parent,
          i18nKey,
        Severity: Minor
        Found in src/Trans.js - About 1 hr to fix

        Cognitive Complexity

        Cognitive Complexity is a measure of how difficult a unit of code is to intuitively understand. Unlike Cyclomatic Complexity, which determines how difficult your code will be to test, Cognitive Complexity tells you how difficult your code will be to read and comprehend.

        A method's cognitive complexity is based on a few simple rules:

        • Code is not considered more complex when it uses shorthand that the language provides for collapsing multiple statements into one
        • Code is considered more complex for each "break in the linear flow of the code"
        • Code is considered more complex when "flow breaking structures are nested"

        Further reading

        Function renderNodes has a Cognitive Complexity of 8 (exceeds 5 allowed). Consider refactoring.
        Open

        function renderNodes(children, targetString, i18n) {
          if (targetString === '') return [];
          if (!children) return [targetString];
        
          // v2 -> interpolates upfront no need for "some <0>{{var}}</0>"" -> will be just "some {{var}}" in translation file
        Severity: Minor
        Found in src/Trans.js - About 45 mins to fix

        Cognitive Complexity

        Cognitive Complexity is a measure of how difficult a unit of code is to intuitively understand. Unlike Cyclomatic Complexity, which determines how difficult your code will be to test, Cognitive Complexity tells you how difficult your code will be to read and comprehend.

        A method's cognitive complexity is based on a few simple rules:

        • Code is not considered more complex when it uses shorthand that the language provides for collapsing multiple statements into one
        • Code is considered more complex for each "break in the linear flow of the code"
        • Code is considered more complex when "flow breaking structures are nested"

        Further reading

        Function hasLoadedNamespace has a Cognitive Complexity of 8 (exceeds 5 allowed). Consider refactoring.
        Open

        export function hasLoadedNamespace(ns, i18n) {
          if (!i18n.languages || !i18n.languages.length) {
            warnOnce('i18n.languages were undefined or empty', i18n.languages);
            return true;
          }
        Severity: Minor
        Found in src/utils.js - About 45 mins to fix

        Cognitive Complexity

        Cognitive Complexity is a measure of how difficult a unit of code is to intuitively understand. Unlike Cyclomatic Complexity, which determines how difficult your code will be to test, Cognitive Complexity tells you how difficult your code will be to read and comprehend.

        A method's cognitive complexity is based on a few simple rules:

        • Code is not considered more complex when it uses shorthand that the language provides for collapsing multiple statements into one
        • Code is considered more complex for each "break in the linear flow of the code"
        • Code is considered more complex when "flow breaking structures are nested"

        Further reading

        Function buildTransElement has 5 arguments (exceeds 4 allowed). Consider refactoring.
        Open

          extracted,
          finalAttributes,
          t,
          closeDefaults = false,
          wasElementWithChildren = false,
        Severity: Minor
        Found in icu.macro.js - About 35 mins to fix

          Avoid too many return statements within this function.
          Open

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

            'index' is defined but never used.
            Open

            function nodesToString(mem, children, index) {
            Severity: Minor
            Found in src/Trans.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 'astNodes'.
            Open

                if (Object.prototype.toString.call(astNodes) !== '[object Array]') astNodes = [astNodes];
            Severity: Minor
            Found in src/Trans.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

            Expected to return a value in arrow function.
            Open

                  clone.children = clone.children.reduce((mem, child) => {
            Severity: Minor
            Found in icu.macro.js by eslint

            Enforces return statements in callbacks of array's methods (array-callback-return)

            Array has several methods for filtering, mapping, and folding. If we forget to write return statement in a callback of those, it's probably a mistake.

            // example: convert ['a', 'b', 'c'] --> {a: 0, b: 1, c: 2}
            var indexMap = myArray.reduce(function(memo, item, index) {
              memo[item] = index;
            }, {}); // Error: cannot set property 'b' of undefined

            This rule enforces usage of return statement in callbacks of array's methods.

            Rule Details

            This rule finds callback functions of the following methods, then checks usage of return statement.

            Examples of incorrect code for this rule:

            /*eslint array-callback-return: "error"*/
            
            var indexMap = myArray.reduce(function(memo, item, index) {
                memo[item] = index;
            }, {});
            
            var foo = Array.from(nodes, function(node) {
                if (node.tagName === "DIV") {
                    return true;
                }
            });
            
            var bar = foo.filter(function(x) {
                if (x) {
                    return true;
                } else {
                    return;
                }
            });

            Examples of correct code for this rule:

            /*eslint array-callback-return: "error"*/
            
            var indexMap = myArray.reduce(function(memo, item, index) {
                memo[item] = index;
                return memo;
            }, {});
            
            var foo = Array.from(nodes, function(node) {
                if (node.tagName === "DIV") {
                    return true;
                }
                return false;
            });
            
            var bar = foo.map(node => node.getAttribute("id"));

            Known Limitations

            This rule checks callback functions of methods with the given names, even if the object which has the method is not an array.

            When Not To Use It

            If you don't want to warn about usage of return statement in callbacks of array's methods, then it's safe to disable this rule. Source: http://eslint.org/docs/rules/

            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

            import React from 'react';
            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/I18nextProvider.js by eslint

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

            Severity
            Category
            Status
            Source
            Language