useLiteralKeys
诊断类别：lint/complexity/useLiteralKeys
¥Diagnostic Category: lint/complexity/useLiteralKeys
自从：v1.0.0
¥Since: v1.0.0
来源：
¥Sources:
-
与以下相同：
dot-notation¥Same as:
dot-notation -
与以下相同：
@typescript-eslint/dot-notation¥Same as:
@typescript-eslint/dot-notation
强制使用文字访问属性而不是计算属性访问。
¥Enforce the usage of a literal access to properties over computed property access.
¥Examples
¥Invalid
a.b["c"];code-block.js:1:5 lint/complexity/useLiteralKeys FIXABLE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✖ The computed expression can be simplified without the use of a string literal.
> 1 │ a.b[“c”];
│ ^^^
2 │
ℹ Unsafe fix: Use a literal key instead.
1 │ - a.b[“c”];
1 │ + a.b.c;
2 2 │
a.c[`d`]code-block.js:1:5 lint/complexity/useLiteralKeys FIXABLE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✖ The computed expression can be simplified without the use of a string literal.
> 1 │ a.c[d]
│ ^^^
2 │
ℹ Unsafe fix: Use a literal key instead.
1 │ - a.c[</strong></span><span style="color: Tomato;"><strong>d</strong></span><span style="color: Tomato;"><strong>]
1 │ + a.c.d
2 2 │
a.c[`d`] = "something"code-block.js:1:5 lint/complexity/useLiteralKeys FIXABLE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✖ The computed expression can be simplified without the use of a string literal.
> 1 │ a.c[d] = “something”
│ ^^^
2 │
ℹ Unsafe fix: Use a literal key instead.
1 │ - a.c[</strong></span><span style="color: Tomato;"><strong>d</strong></span><span style="color: Tomato;"><strong>]·=·“something”
1 │ + a.c.d·=·“something”
2 2 │
a = { ['b']: d}code-block.js:2:3 lint/complexity/useLiteralKeys FIXABLE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✖ The computed expression can be simplified to a string literal.
1 │ a = {
> 2 │ [‘b’]: d
│ ^^^
3 │ }
4 │
ℹ Unsafe fix: Use a literal key instead.
1 1 │ a = {
2 │ - → [‘b’]:·d
2 │ + → “b”:·d
3 3 │ }
4 4 │
¥Valid
a["c" + "d"];a[d.c];¥Related links