Proposing a "computed-property-as-needed" rule

With ES6 Computed Properties, one can do the following:

let prop = 'b';
return {
  'a': 1,
  [prop]: 2,
  c: 3,
  ['d']: 4
}

Note how the brackets around the ['d'] property are superfluous. It could instead be written as 'd' or d.

When does this rule warn? Please describe and show example code:

If enabled, the following would trigger:

{
  ['x']: 1
}

Any property which does not need to be computed could trigger the rule.

Is this rule preventing an error or is it stylistic?

Stylistic

Why is this rule a candidate for inclusion instead of creating a custom rule?

This rule affects basic ES6 syntax for situations where there are two equivalent ways to write the same code.

Are you willing to create the rule yourself?

I will attempt to if nobody else is interested.

[mysticatea]

Or just no-useless-computed-property. That rule would be very similar to dot-notation rule.

[tlhunter]

Thanks, @BYK!