-
Notifications
You must be signed in to change notification settings - Fork 47
chore: unify linting and formatting configs #1420
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
chore: unify linting and formatting configs #1420
Conversation
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.
lgtm
87187a6 to
dfdd7b9
Compare
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## master #1420 +/- ##
==========================================
- Coverage 62.93% 62.36% -0.57%
==========================================
Files 128 128
Lines 3399 3329 -70
Branches 906 901 -5
==========================================
- Hits 2139 2076 -63
+ Misses 1141 1132 -9
- Partials 119 121 +2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
04874c3 to
ae2c4cf
Compare
Unifying configs across the Patch and content-sources-frontend repositories. Patch now uses Prettier for formatting and ESLint for quality rules only. ESLint has also been upgraded to v9.
Adjust the commitlint config to use the 50/72 rule similarly to the content-sources-frontend repository
This commit enforces the `import/no-duplicates` rule in ESLint with auto-fix enabled.
ae2c4cf to
575daa5
Compare
Issues attributed to commits in this pull requestThis pull request was merged and Sentry observed the following issues: |
Description
Configuration Alignment
/* global ... */comments by moving environment settings into the main ESLint fileTool Modernization and Scope
/srcdirectory, excluding the/configfolder to prevent issues with older conventionsGit
commitlintconfig to enforce the 50/72 rule for commit message formatting, aligning with the content-sources-frontend repositoryHow to test the PR
npm run lint:js:fix,npm run lint:sassandnpm run prettier:checkwill be a message confirming that all linting and formatting rules have been satisfied.Checklist: