Tutorial on block deprecation #67
Replies: 4 comments
-
|
🙋♂️ Flagging that I'd be happy to take on authorship of this, so I haven't added the "needs writer" label. |
Beta Was this translation helpful? Give feedback.
-
|
That's a great topic @mburridge - I feel many block developers shy away entirely just because it's not well understood and create dynamic blocks instead. |
Beta Was this translation helpful? Give feedback.
-
|
This is now in the works. #71 and this discussion is locked. Please continue discussion on the issue. |
Beta Was this translation helpful? Give feedback.
-
|
Published: Block deprecation – a tutorial |
Beta Was this translation helpful? Give feedback.
-
If you make a change to the way that a block is rendered you will see the "invalid content" error message after the change.
This commonly occurs during development, and developers working with blocks are very aware of this and are used to dealing with it.
However, if you've already published a block and want to make changes to it in an update you won't want users to see the "invalid content" error message, which they will in each instance of the block across their site until recovery is done on each of them.
To circumvent this problem developers can "deprecate" the old version of the block.
A tutorial on how to deprecate a block, and when and why you should do it, would be a nice addition to the Developer Blog.
Reference:
Deprecation
Beta Was this translation helpful? Give feedback.
All reactions