-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Add new package @wordpress/stylelint config
#22777
Conversation
…g-end-of-source-newline` rule instead. (#84)
* feat: Add SCSS preset config * fix: Include README.md and scss.js in package.json files list * test: Add initial SCSS tests
… a promise and move css code out of tests to individual files * feat: Use ECMAScript 8/2017 * refactor: Use async/await instead of returning a promise and move css code out of tests to individual files
* chore(package): update ava to version 0.17.0 * refactor: Include path to test fixtures https://greenkeeper.io/
* chore(package): update eslint-config-stylelint to version 6.0.0 * refactor: Update tests per latest `eslint-config-stylelint`
…118) * chore: Drop NodeJS from Travis CI * chore: Drop NodeJS from AppVeyor * chore: Bump minimum NodeJS requirement to 6.9.1
@ntwb, would be best to answer the version question. In the past, we migrated other packages and applied the major version bump. I don't mind following the same approach here. |
So that would be 18.0.0? That works for me too. This would also allow us to reduce the version constraints in peerDependencies so we can publish this with the fix from WordPress-Coding-Standards/stylelint-config-wordpress#267. |
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.
Overall, it looks like it's ready to merge. It's hard to tell if functionality wise everything is correct as I have no idea what the package contains as of today. If @ntwb or anyone else maintaining is happy then I'm happy as well 😃
@@ -0,0 +1,22 @@ | |||
The MIT License (MIT) |
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.
Is this license file necessary? It looks like a standard one. I have no idea myself, just asking. We don't put copies for "GPL-2.0-or-later" in other packages.
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.
Good question, I'm not sure either. Wondering who would be best to answer this?
At least the license itself says, that it should be included. But the copyright info is actually a bit odd. 🤷🏻♂️
I left a few more nitpicks among which I care mostly about the version bump one 😄 Once it's addressed I'm happy to approve this PR based on my limited knowledge as raised in the previous comment. |
I have just published WordPress packages to npm. When running
Is it covered in this PR? If not, I opened an issue: #27775. |
@gziolo Yes and no, referencing #22777 (comment) again. |
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.
Once CI is green this PR should be good to go. Some e2e tests became unstable but changes proposed here should not have impact on them at all. You might need to restart them when they fail.
@gziolo I can't get |
Yes, it's failing on the majority CI checks now 🤷♂️ I merged PR regardless 😃 |
Description
Migrates the WordPress-Coding-Standards/stylelint-config-wordpress into this repo as a new
@wordpress/stylelint-config
package usinglerna import
Import Repo
Using Lerna the existing git repo was imported using:
Note: As such this PR includes a lot of commits, the oldest 320 commits are from the legacy repo
Testing
To test run the following standalone tests:
node_modules
,rm -rf node_modules
npm install
npm run build
npm run lint-css
from the repo rootnpm run test-unit
from the repo rootToDo
author
fieldwp-scripts format-css
Update packages per /packages#managing-dependencies
@wordpress/scripts
packagesHow has this been tested?
Screenshots
Types of changes
Checklist: