Rule expansion proposal: Add "allowPattern" option to either `quote-props` or `no-useless-computed-key`

Currently the dot-notation rule has an allowPattern option to, for example, allow bracket notation when camel-case is enabled and a property must be in snake_case. It’s the exact same use case for either quote-props or no-useless-computed-key; when building an object for an external api, sometimes you have to use snake_case. Whether that more properly belongs in one or the other, I’m not sure.

Without this change, the only way to put snake case’d params into an object for third party consumption when you have the camel case rule enabled is to just create the object and add properties, which is a bit of a hassle.

Compare:

const obj = {};
obj['foo_bar'] = true;
obj['bar_foo'] = false;
thirdPartyApi(obj);

vs

thirdPartyApi({
  'foo_bar': true,
  'bar_foo': false
});

or

thirdPartyApi({
  ['foo_bar']: true,
  ['bar_foo']: false
});

[sgtpepper43]

It’s good, it’s good, thinning out the backlog makes it more likely that if this comes up again it would get noticed (and makes it more likely that more important issues would get noticed), so it’s definitely a good thing.

[kaicataldo]

That’s the goal! Stale issues make it harder both for us as a team to prioritize what we should work on and make it harder for contributors to find issues to work on themselves.