Block library: Introduce block.json metadata for all client side blocks #14770
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR is a follow-up for #14551 which introduced a way to inline
block.json
metadata.Scope covered by this PR:
block.json
files for the following fields:name
category
attributes
There were 2 exceptions where I couldn't easily move
attributes
to JSON file:default
value for an attribute (https://github.com/WordPress/gutenberg/blob/master/packages/block-library/src/file/index.js#L64-L69)I opened separate PRs for them: #14862 and #14863.
How has this been tested?
npm run test
npm run dev
and ensure all blocks work as before.