eslint/no-useless-computed-key Style

🚧 An auto-fix is still under development.

What it does

Disallow unnecessary computed property keys in objects and classes

Why is this bad?

It’s unnecessary to use computed properties with literals such as:

const foo = { ["a"]: "b" };

The code can be rewritten as:

const foo = { "a": "b" };

Examples

Examples of incorrect code for this rule:

const a = { ["0"]: 0 };
const b = { ["0+1,234"]: 0 };
const c = { [0]: 0 };
const e = { ["x"]() {} };

class Foo {
  ["foo"] = "bar";
  [0]() {}
  static ["foo"] = "bar";
  get ["b"]() {}
  set ["c"](value) {}
}

Examples of correct code for this rule:

const a = { "a": 0 };
const b = { 0: 0 };
const c = { x() {} };
const e = { "0+1,234": 0 };

class Foo {
  "foo" = "bar";
  0() {}
  "a"() {}
  static "foo" = "bar";
}

Examples of additional correct code for this rule:

const c = {
  "__proto__": foo, // defines object's prototype
  ["__proto__"]: bar, // defines a property named "__proto__"
};
class Foo {
  ["constructor"]; // instance field named "constructor"
  "constructor"() {} // the constructor of this class
  static ["constructor"]; // static field named "constructor"
  static ["prototype"]; // runtime error, it would be a parsing error without `[]`
}

Options

enforceForClassMembers

{ type: boolean, default: true }

The enforceForClassMembers option controls whether the rule applies to class members (methods and properties).

Examples of correct code for this rule with the { "enforceForClassMembers": false } option:

class SomeClass {
  ["foo"] = "bar";
  [42] = "baz";
  get ["b"]() {}
  set ["c"](value) {}
  static ["foo"] = "bar";
}

How to use

To enable this rule in the CLI or using the config file, you can use:

CLI

oxlint --deny no-useless-computed-key

Config (.oxlintrc.json)

{
  "rules": {
    "no-useless-computed-key": "error"
  }
}

References

• Rule Source