-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Block library: Extract deprecated
field to their own files
#15057
Conversation
a5b76bf
to
41aae71
Compare
It's a bit hard to review this without any tests for deprecated blocks. Would it be possible to add some simple tests to see if deprecated block structures are converted correctly? |
Good idea. I will add something based on the existing fixtures. I think Columns and Paragraph block have some coverage already: |
Blocked by #15268. |
41aae71
to
9f5c46c
Compare
9f5c46c
to
9fa63c9
Compare
Based on my question #15268 (comment):
I can confirm that we those deprecations won't work anymore for |
Description
Part of aligning block library to Block Registration API RFC #13693.
It's all about moving
deprecated
fields to their own file to follow the proposal drafted in RFC.Updated blocks:
Gallery
Image
Removed block deprecations
Heading
- see Block library: Extractdeprecated
field to their own files #15057 (comment)List
- see Block library: Extractdeprecated
field to their own files #15057 (comment)How has this been tested?
npm test
npm run test-e2e
Manually tested whether all blocks load as before.