Skip to content
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

Update filenames #578

Merged
merged 10 commits into from
Nov 25, 2024
Merged

Update filenames #578

merged 10 commits into from
Nov 25, 2024

Conversation

gracepark
Copy link
Contributor

@gracepark gracepark commented Nov 25, 2024

The filenames plugin is no longer maintained, and I was running into an issue that fixupPluginRules would not fix for us using the compat utility in eslint v9. It needs the schema:

https://github.com/github/eslint-plugin-github/pull/578/files#diff-b1acaab48d8385d990537662bf4fa3dd489b8974367f0628147c83977534feb4R13

Since the plugin is no longer being maintained, I decided to bring that particular regex rule into the github rules with the fix so that we no longer need to rely on the filename plugin.

@gracepark gracepark requested a review from a team as a code owner November 25, 2024 19:59
eslint.config.js Outdated
@@ -23,7 +23,7 @@ module.exports = [
plugins: {
eslintPlugin,
importPlugin,
filenames,
filenamesPlugin: fixupPluginRules(filenames),
Copy link
Contributor

Choose a reason for hiding this comment

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

does it matter that it's not a string like 'i18n-text' on the next line?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That should be okay - what I ended up doing was bringing in the filenames match regex rule into github. The filenames plugin is no longer supported and the compat utility was not working for our rule configuration.

Copy link
Contributor

@arelia arelia left a comment

Choose a reason for hiding this comment

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

added one comment i'm not sure about but otherwise looks good

Copy link
Contributor

@arelia arelia 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, but I'm not familiar with how GitHub does open source so I wonder if it matters that the filenames plugin didn't have a LICENSE.md and is there anything else we should do when bringing it over. It might be worth pinging the team

@gracepark gracepark merged commit 97908fc into main Nov 25, 2024
7 checks passed
@gracepark gracepark deleted the filenames-fix branch November 25, 2024 22:31
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