-
Notifications
You must be signed in to change notification settings - Fork 808
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
Extensions: Simplify directories #11971
Conversation
Thank you for the great PR description! When this PR is ready for review, please apply the Scheduled Jetpack release: April 29, 2019. |
extensions/shared/README.md
Outdated
|
||
## registerJetpackPlugin() | ||
|
||
This util will only register a Gutenberg plugin if it meets the availability requirements described above. |
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.
We probably need to tell about these methods in more visible /extensions/README.md
as part of documentation to get folks started building blocks? Good here for now tho.
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 think i can drop these method descriptions altogether in favor of standard docblocks.
*/ | ||
export function hasStyleClass( classNames = '' ) { | ||
return classNames.split( ' ' ).some( className => className.startsWith( 'is-style-' ) ); | ||
} |
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.
Confirmed that these are not used anywhere; I think they used to be in Tiled gallery.
Well spotted!
@@ -6,7 +6,7 @@ import { registerBlockType } from '@wordpress/blocks'; | |||
/** | |||
* Internal dependencies | |||
*/ | |||
import extensionList from '../setup/index.json'; | |||
import extensionList from '../index.json'; |
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.
Nice move, like this people will find this right away when they start developing blocks.
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.
Super clear and builds nicely 👍
Tested:
yarn run build-extensions
yarn run test-extensions
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.
Ran the build and spot-check the post editor, so far so good.
I'm manually setting this to allow merging overriding the failed wpcom check. Since this is a big change, please merge when you have the bandwidth to make the wp.com merge happen. I'm forcing a diff to be created, but due to other Jetpack changes that didn't merge yet, we're running into conflicts.
Caution: This PR has changes that must be merged to WordPress.com |
We were removing some test files from wpcom (they don't need to be synced) so might be that's why there was a conflict D26665-code & D26669-code |
8fb8572
to
89e865e
Compare
Rebased and manually updated D26668-code Everything is still building well! @kraftbj can you re-bless this? |
89e865e
to
5f270d1
Compare
Rebased here, rebased D26668-code and it applies nicely in the sandbox. |
Fixes a small thread of dignity
Changes proposed in this Pull Request:
extensions/setup
and puts its content in either the root of the extensions folder, or inextensions/shared
extensions/utils
and puts its content inextensions/shared
Testing instructions:
yarn build
and get no errorsProposed changelog entry for your changes: