-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Improve JS package descriptions #8121
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,7 @@ | ||
{ | ||
"name": "@wordpress/components", | ||
"version": "1.0.1", | ||
"description": "UI Compoonents for WordPress", | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 😅 |
||
"description": "UI components for WordPress", | ||
"author": "The WordPress Contributors", | ||
"license": "GPL-2.0-or-later", | ||
"keywords": [ | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,7 @@ | ||
{ | ||
"name": "@wordpress/compose", | ||
"version": "1.0.1", | ||
"description": "WordPress Higher Order components", | ||
"description": "WordPress higher-order components", | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'd add "(HOC)" in brackets here; lots of people throw that acronym around and giving newbies context here for free is 👍 |
||
"author": "The WordPress Contributors", | ||
"license": "GPL-2.0-or-later", | ||
"keywords": [ | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,7 @@ | ||
{ | ||
"name": "@wordpress/keycodes", | ||
"version": "1.0.1", | ||
"description": "KeyCodes utilities for WordPress", | ||
"description": "Keycodes utilities for WordPress", | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This one, I think, could be expanded upon further ("Keycodes utilities for WordPress; used to check for keyboard events across browsers/operating systems") |
||
"author": "The WordPress Contributors", | ||
"license": "GPL-2.0-or-later", | ||
"keywords": [ | ||
|
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.
Interesting, I'd have thought sentence-case would be better for those. Some descriptions are surely multi-sentence?
It's split on NPM (React seems to be all without periods; lodash all with, etc.)
Given we're in the "comments must have full-stops" camp (I like it), maybe we should be here too? 🤷♂️
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.
I would be also happy to see this change.
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.
Seems like something that would be good to have (though from what I can tell, not yet offered as a feature) from
npm-package-json-lint
, which we're already using and have a predefined configuration for.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.
Hey! I just released v3.3.0 of
npm-package-json-lint
with a newdescription-format
rule. It has two options:requireCapitalFirstLetter
- Throws an error if the first character in the description isn't capitalized.requireEndingPeriod
- Throws an error if the description doesn't end with a period.Hopefully this works well for your team!
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.
Thanks, opened PR to start using this new rule: #8596.