Back to Eslint

no-ex-assign

docs/src/rules/no-ex-assign.md

10.3.0751 B
Original Source

If a catch clause in a try statement accidentally (or purposely) assigns another value to the exception parameter, it is impossible to refer to the error from that point on. Since there is no arguments object to offer alternative access to this data, assignment of the parameter is absolutely destructive.

Rule Details

This rule disallows reassigning exceptions in catch clauses.

Examples of incorrect code for this rule:

::: incorrect

js
/*eslint no-ex-assign: "error"*/

try {
    // code
} catch (e) {
    e = 10;
}

:::

Examples of correct code for this rule:

::: correct

js
/*eslint no-ex-assign: "error"*/

try {
    // code
} catch (e) {
    const foo = 10;
}

:::

Options

This rule has no options.