Block library: Extract deprecated field to their own files (p.2)#15071
Merged
Block library: Extract deprecated field to their own files (p.2)#15071
deprecated field to their own files (p.2)#15071Conversation
e717ecb to
9e6ed25
Compare
Member
Author
|
Blocked by #15268. |
9e6ed25 to
30d5642
Compare
30d5642 to
8fa1405
Compare
Member
Author
|
It's ready for review after integration tests were added in #15268. |
youknowriad
approved these changes
May 21, 2019
14 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Part of aligning block library to Block Registration API RFC #13693.
It's all about moving
deprecatedfields to their own file to follow the proposal drafted in RFC.Updated blocks:
ParagraphPullquoteQuoteHow has this been tested?
npm testnpm run test-e2eManually tested whether all blocks load as before.