* eslint: enable no bracket notation rule
Enable code-no-bracket-notation-for-identifiers for JavaScript and TypeScript files while grandfathering the 509 files with existing violations in a CODEOWNERS-gated allowlist.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* eslint: update bracket allowlist owners
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* eslint: group bracket notation exclusions
Organize the existing baseline by feature area so cleanup can be tracked and assigned without changing the excluded file set.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* eslint: test no bracket notation rule
Add RuleTester coverage for valid accesses, diagnostics, and autofix edge cases. Preserve escaped string-literal property names by checking their raw source before reporting.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* eslint: fix bracket notation in language extensions
Replace identifier-safe bracket notation across language feature extensions and remove the completed group from the temporary allowlist.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
For #269213
This adds a new eslint rule for `as any` and `<any>({... })`. We'd like to remove almost all of these, however right now the first goal is to prevent them in new code. That's why with this first PR I simply add `eslint-disable` comments for all breaks
Trying to get this change in soon after branching off for release to hopefully minimize disruption during debt week work
Dmitriy VasyuraandCopilot
Martin Aeschlimann
Matt Bierner
Johannes Rieken
Cameron Little