id-match requires separate config for property name

[tinymins]

What rule do you want to change?
id-match

Does this change cause the rule to produce more or fewer warnings?
Yes

How will the change be implemented? (New option, new default behavior, etc.)?
New option

Please provide some example code that this change will affect:

/* eslint id-match: [2, "^[^_][a-zA-Z]*$", { 
  "propertiesPattern": "^[a-z_][a-zA-Z]*$",
  "errorMessage": "Identifier '{{name}}' is not in camelcase.",
  "propertiesErrorMessage": "Properties identifier '{{name}}' is not in lower camelcase."
}] */
// bad
const _A = { a: 1 };
const _A = { _a: 1 };
const A = { a_b: 1 };
const A = { B: 1 };

// good
const A = { a: 1 };
const A = { _a: 1 };
const A = { aB: 1 };
const A = { b: 1 };

What does the rule currently do for this code?
Cannot separate var name with prop name, sometimes we want to allow underscore in prop names but not in normal var names.

What will the rule do after it's changed?
Additional config added, no affect for prev version.

Are you willing to submit a pull request to implement this change?
Yes

[tinymins]

#10477

[g-plane]

Hey @tinymins , thanks for the issue.

Alternatively, you can consider camelcase and set "properties" false.

[tinymins]

Hey @tinymins , thanks for the issue.

Alternatively, you can consider camelcase and set "properties" false.

Hi, @g-plane #10473

[eslint-deprecated]

Unfortunately, it looks like there wasn't enough interest from the team
or community to implement this change. While we wish we'd be able to
accommodate everyone's requests, we do need to prioritize. We've found
that issues failing to reach accepted status after 21 days tend to
never be accepted, and as such, we close those issues.
This doesn't mean the idea isn't interesting or useful, just that it's
not something the team can commit to.

Thanks for contributing to ESLint and we appreciate your understanding.