Skip to content

Conversation

@gribnoysup
Copy link
Collaborator

Not intended for review, opening just to kick off CI and track the progress on this work. I'm going to split it ino smaller chunks that should be easier to review and merge

@github-actions github-actions bot added the fix label Nov 25, 2025
@gribnoysup gribnoysup changed the title fix(eslint): update eslint to latest and resolve all new issues fix(eslint): update eslint plugins to latest and resolve all new issues Nov 25, 2025
Copy link
Collaborator

@addaleax addaleax left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good so far!

import type { FetchStatus } from '../utils/fetch-status';

import { FetchReasons } from '../utils/fetch-reason';
import type { FetchReason } from '../utils/fetch-reason';
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would be nice if we could go the other route and remove the enums, is that an option here?

Copy link
Collaborator Author

@gribnoysup gribnoysup Nov 25, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was looking at these newly triggered errors and had the same thought, but I think it would be too big of a change just for a valuable otherwise eslint deps version update to be honest... I'm on board for finding a way to move away from them. Maybe we can prohibit the syntax right away and make exception for existing ones, then slowly start removing them? Something like this sounds reasonable?

@gribnoysup gribnoysup force-pushed the update-eslint-to-latest-and-resolve-new-warnings branch 4 times, most recently from 4e1ec38 to 2e61807 Compare November 25, 2025 15:40
@gribnoysup gribnoysup force-pushed the update-eslint-to-latest-and-resolve-new-warnings branch from 2e61807 to 71cf178 Compare November 25, 2025 15:40
@gribnoysup gribnoysup closed this Dec 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants