-
Notifications
You must be signed in to change notification settings - Fork 35
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
First cut of ESLint upgrade #1047
Conversation
🦋 Changeset detectedLatest commit: 92e5410 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
}; | ||
const baseConfig = [ | ||
{ | ||
ignores: [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Worth considering if you migrate this on behalf of users (any custom .eslintignore they have) in some form, or just say "use dangerouslySetESLintConfig" or similar
path.join(skuPackagePath, 'config/eslint/importOrderConfig.js'), | ||
]); | ||
}); | ||
it.todo('should generate a eslint config'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was too lazy to fix this test :) and one below
@AaronMoat I was working off this branch 😅. Feel free to keep the PR/branch around. |
Sorry @askoufis! |
Closing the PR but keeping the branch. I'll probably be force-pushing over it soon ™️ |
I don't currently intend to fully perform this upgrade on behalf of the sku maintainers, but I wanted to do a first cut of the upgrade to make sure seek-oss/eslint-config-seek#145 wasn't horribly wrong. It seems ok?