Do you have any advice on how to handle existing plugin blocks when a feature that was implemented in a plugin is implemented in the core?

[kohheepeace]

It's just like the title says,

Do you have any advice on how to handle existing plugin blocks when a feature that was implemented in a plugin is implemented in the core?

For example, the core currently has the following new block PRs/issues

• New block: Link Preview #47765
• New block: Accordion block #21584

But consider if this functionality was already provided by a plugin.

Do you have any advice on migration, etc... in this case? Sorry for the sketchy question. 😢

@Mamaduka any thoughts about your plugin ?

• https://github.com/Mamaduka/bookmark-card

[Mamaduka]

You can continue supporting your existing plug-in if it has different enough features. I might consider doing that for a Bookmark Card.

Other options:

• Provide a transformation option to the new core block. This requires explicit action from the user, and they can remove the plug-in once all transformations are done.
• Use the useMigrateOnLoad technique. It will migrate the existing block to a new one, a post containing that block. This is not an explicit action, and not all users might want to migrate, so be considerate when implementing it.

[kohheepeace]

Super thanks for your concise and clear answer! It is very helpful 💯