pve-eslint/eslint/docs/rules/no-const-assign.md
Dominik Csapak eb39fafa4f first commit
includes a (minimal) working wrapper

Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
2020-04-06 15:06:03 +02:00

69 lines
1.3 KiB
Markdown

# Disallow modifying variables that are declared using `const` (no-const-assign)
We cannot modify variables that are declared using `const` keyword.
It will raise a runtime error.
Under non ES2015 environment, it might be ignored merely.
## Rule Details
This rule is aimed to flag modifying variables that are declared using `const` keyword.
Examples of **incorrect** code for this rule:
```js
/*eslint no-const-assign: "error"*/
/*eslint-env es6*/
const a = 0;
a = 1;
```
```js
/*eslint no-const-assign: "error"*/
/*eslint-env es6*/
const a = 0;
a += 1;
```
```js
/*eslint no-const-assign: "error"*/
/*eslint-env es6*/
const a = 0;
++a;
```
Examples of **correct** code for this rule:
```js
/*eslint no-const-assign: "error"*/
/*eslint-env es6*/
const a = 0;
console.log(a);
```
```js
/*eslint no-const-assign: "error"*/
/*eslint-env es6*/
for (const a in [1, 2, 3]) { // `a` is re-defined (not modified) on each loop step.
console.log(a);
}
```
```js
/*eslint no-const-assign: "error"*/
/*eslint-env es6*/
for (const a of [1, 2, 3]) { // `a` is re-defined (not modified) on each loop step.
console.log(a);
}
```
## When Not To Use It
If you don't want to be notified about modifying variables that are declared using `const` keyword, you can safely disable this rule.