-
Notifications
You must be signed in to change notification settings - Fork 813
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
Blocks: update all blocks to use namespaces and constants for consistency #15088
Conversation
date( $time_format, $opening ), | ||
date( $time_format, $closing ) | ||
gmdate( $time_format, $opening ), | ||
gmdate( $time_format, $closing ) |
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.
This was necessary as it was triggering a PHPCS error that stopped me from committing.
Thank you for the great PR description! When this PR is ready for review, please apply the Scheduled Jetpack release: April 7, 2020. |
* Tiled Gallery block. Depends on the Photon module. | ||
* Tiled Gallery block. | ||
* Relies on Photon, but can be used even when the module is not active. |
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 took the opportunity to update this since it wasn't valid anymore since #13471.
Caution: This PR has changes that must be merged to WordPress.com |
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.
Looked at the code and tested the blocks. Looks fine to me!
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.
Able to add and save a number of blocks. No items in the PHP log.
Marked as needing author reply so we can restart Travis and get wpcom Fusion happy, but it can be merged once those things are green. |
jeherve, Your synced wpcom patch D40681-code has been updated. |
Fixes #14843 This should keep things consistent by having all blocks registered the same way.
See p1584972801038800-slack-jetpack-crew
6b144fe
to
d87b3a6
Compare
jeherve, Your synced wpcom patch D40681-code has been updated. |
r204659-wpcom |
Fixes #14843
Changes proposed in this Pull Request:
This PR does not introduce any new functionality or changes anything in the way the blocks work today. It does, however, change the way blocks are registered to bring all blocks to the same level and be consistent across all blocks. It should help new Jetpack contributors who work on blocks, by giving them one approach they can follow to register a new block.
Automattic\Jetpack
namespace (vs. justJetpack
before, or no namespace at all). Adding the vendor name to the namespace is how we work with all other namespaces in Jetpack. Part of me wonders if we shouldn't introduce one more level there, so all blocks live under anAutomattic\Jetpack\Blocks
orAutomattic\Jetpack\Extensions
namespace. It may make things easier if one day we move those blocks into a package.Testing instructions:
Proposed changelog entry for your changes: