cannot assign variables from destructure with camelCase rule `ignoreDestructure` set to true

I am reopening #11226 as suggested at the end of that issue to bring this to light again. The problem can be seen here. Basically though you cannot assign any variable that is not camel cased from a destructured statement:

  /* eslint camelcase: [error, { ignoreDestructuring: true, properties: "never" }] */

  const { field_formatted_text } = someObject;

  const underscoreOnObjectProperty = {
    abc: field_formatted_text . // this is fine
  };
  
  // throws: Identifier 'field_formatted_text' is not camel case
  const myVar = field_formatted_text + 'abc';

There is an obvious solution to just rename the variable when it’s destructured:

  const { field_formatted_test: fieldFormattedText } = someObject;

However, this is annoying to have to do and you may also lose semantic meaning from the different cases (i.e. variables returned from an api).

Thanks in advance!

[kaicataldo]

@DMR-coding The options for this rule currently only toggles the behavior for when new variables are created. This means that other references to the variable aren’t affected, which leads to the somewhat confusing behavior of the rule not warning on, say, destructured assignments, but will then warn when the variable is actually used.

[mdjermanovic]

I believe it would be better to open a ‘Rule change request’ issue with a backward-compatible enhancement proposal.

Destructuring creates new variables that might be used many times in the rest of the code. A change to allow underscores in this case (instead of enforcing the user to ‘rename variables’ in the destructuring pattern) without opt-in might be undesirable for some users.