[wp-trac] [WordPress Trac] #47620: REST API: Expose blocks registered on the server
WordPress Trac
noreply at wordpress.org
Mon Dec 2 09:03:19 UTC 2019
#47620: REST API: Expose blocks registered on the server
-------------------------------------------------+-------------------------
Reporter: gziolo | Owner:
| spacedmonkey
Type: feature request | Status: assigned
Priority: normal | Milestone: Future
| Release
Component: REST API | Version: 5.0
Severity: normal | Resolution:
Keywords: has-patch has-unit-tests dev- | Focuses: rest-api
feedback |
-------------------------------------------------+-------------------------
Comment (by koke):
To clarify the mobile perspective, we are currently not loading any code
from the server. We have doubts that the [https://developer.apple.com/app-
store/review/guidelines/#third-party-software App Store Guidelines would
allow us to do so]. The current approach is that we are shipping the code
for the core blocks we support with the apps. Once we have enough to
support plugins, the idea is to start doing the same for the most
popular/requested plugins and ship their code alongside the apps.
That's why we need a version to know which code matches to a specific
block. We have already run into issues with that recently. Whenever a
block markup changes, Gutenberg is designed to deal with backwards
compatibility and migrate that content automatically. However, it might be
the case that you try to open a block created with the newer markup with
an older client, leading to "invalid content".
This can happen both ways: people might upgrade their site before their
apps, but also we are currently developing gutenberg-mobile against
master, so users would get updated on mobile way before they do on their
sites, unless they are running the plugin.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/47620#comment:22>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list