[wp-trac] [WordPress Trac] #52192: REST API: Add batch image editing
WordPress Trac
noreply at wordpress.org
Mon Feb 1 19:25:59 UTC 2021
#52192: REST API: Add batch image editing
-------------------------------------+-----------------------
Reporter: ajlende | Owner: antpb
Type: enhancement | Status: reopened
Priority: normal | Milestone: 5.7
Component: REST API | Version: trunk
Severity: normal | Resolution:
Keywords: has-patch needs-testing | Focuses:
-------------------------------------+-----------------------
Comment (by TimothyBlynJacobs):
> The plugin page suggests 5.3. Typically we check for feature support and
patch in the required updates if it isn't available. I'll have to include
that in the GB PR before it gets merged.
The plugins page is outdated:
https://github.com/WordPress/gutenberg/issues/28075
@SergeyBiryukov AFAIK, we haven't deprecated any REST API parameters yet,
this is the first. At a later point I plan on adding a more formal
`deprecated` syntax that we could apply to the parameter schemas. So at
the moment, this is just a soft deprecation.
The problem generally is that we don't have a good way to generate
changelogs for the REST API. We could add `@since` markers, but they
aren't picked up by the [https://developer.wordpress.org/rest-
api/reference/ REST API reference] documentation. We also haven't really
done this in the past. AFAICT the only usages are in
`WP_REST_Posts_Controller::get_collection_params()`. Ideally, we'd make
this available in the schema definition for each parameter.
Putting `Deprecated` in the parameter description means that it will be
picked up by the REST API reference. Though for some reason, the edit
endpoint isn't being picked up at all. I'll take a look at that when we
regenerate our docs for 5.7.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/52192#comment:19>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list