Open Issues Need Help
View All on GitHub:sparkles: Monorepo for all the tooling which enables ESLint to support TypeScript
:sparkles: Monorepo for all the tooling which enables ESLint to support TypeScript
:sparkles: Monorepo for all the tooling which enables ESLint to support TypeScript
:sparkles: Monorepo for all the tooling which enables ESLint to support TypeScript
:sparkles: Monorepo for all the tooling which enables ESLint to support TypeScript
:sparkles: Monorepo for all the tooling which enables ESLint to support TypeScript
:sparkles: Monorepo for all the tooling which enables ESLint to support TypeScript
AI Summary: The task is to improve the error message of the `@typescript-eslint/no-unsafe-assignment` rule. Currently, the message incorrectly states that an unsafe array destructuring is occurring when an object destructuring is actually the source of the problem. The fix involves modifying the rule's error message to accurately reflect that an object destructuring with an `any` type is unsafe.
:sparkles: Monorepo for all the tooling which enables ESLint to support TypeScript