Skip to content

chore(eslint): re-enable no-unused-vars for catch blocks; re-enable no-redundant-type-constituents and clean up redundant COMPASS-9459 #7023

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

gribnoysup
Copy link
Collaborator

@gribnoysup gribnoysup commented Jun 13, 2025

That was the most annoying one (so far) and I messed it up a bit by accidentally doing two rules in one go. The bulk of the changes here just cleans up unused errors in catch blocks, another one is removing redundant type definitions (things like unknown | string where unknown just overridese everything), to make this straightforward I'm just cleaning those up instead of trying to address any of them

…le no-redundant-type-constituents and clean up redundant
@gribnoysup gribnoysup requested a review from a team as a code owner June 13, 2025 15:39
@gribnoysup gribnoysup changed the title chore(eslint): re-enable no-unused-vars for catch blocks; re-enable no-redundant-type-constituents and clean up redundant chore(eslint): re-enable no-unused-vars for catch blocks; re-enable no-redundant-type-constituents and clean up redundant COMPASS-9459 Jun 13, 2025
@gribnoysup gribnoysup merged commit 3f4fbbf into main Jun 16, 2025
53 of 54 checks passed
@gribnoysup gribnoysup deleted the eslint-enable-no-unused-vars-no-redundant-type-constituents branch June 16, 2025 13:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants