Skip to content

TINY-11824: Upgrade plugin to support eslint V9 and flat config #52

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
merged 5 commits into from
Apr 28, 2025

Conversation

hamza0867
Copy link
Contributor

@hamza0867 hamza0867 commented Apr 18, 2025

Related Ticket: TINY-11824

Description of Changes:

  • Upgrade the plugin to support eslint V9 and flat config

Pre-checks:

  • Changelog entry added
  • package.json version bumped (if first change of new major/minor)
  • Tests have been added (if applicable)

@hamza0867 hamza0867 requested review from a team, lorenzo-pomili, HAFRMO and michalnieruchalski-tiugo and removed request for a team April 18, 2025 14:42
@hamza0867 hamza0867 requested a review from tiny-james April 25, 2025 10:05
@hamza0867 hamza0867 merged commit cb80de0 into main Apr 28, 2025
5 checks passed
@hamza0867 hamza0867 deleted the feature/TINY-11824 branch April 28, 2025 08:05
Comment on lines +59 to +61
{ messageId: 'noDirectEditorEvents' },
{ messageId: 'noDirectEditorEvents' },
{ messageId: 'noDirectEditorEvents' }
Copy link
Member

Choose a reason for hiding this comment

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

I thought I had submitted this, but github uses the same colour for pending and outdated comments so I didn't notice my request was not blocking merge 🤦

Not sure what to do with this now. New ticket I suppose?


Even if this is how eslint works now, messageId tests are only an acceptable replacement if you also verify that the IDs map to the messages we expect

  • Add ID to console message checks for each of these

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.

4 participants