[wp-trac] [WordPress Trac] #51126: Document the update offer parameter for auto updates
WordPress Trac
noreply at wordpress.org
Fri Nov 19 00:29:18 UTC 2021
#51126: Document the update offer parameter for auto updates
-------------------------------------+------------------------
Reporter: johnbillion | Owner: desrosj
Type: enhancement | Status: reviewing
Priority: normal | Milestone: 5.9
Component: Upgrade/Install | Version:
Severity: normal | Resolution:
Keywords: has-patch needs-refresh | Focuses: docs
-------------------------------------+------------------------
Comment (by dd32):
Replying to [comment:18 desrosj]:
> I also forgot to add that I'm not sure if there are additional fields
that could be returned for each of these types that I haven't encountered
in my testing.
I think you're on the money with your descriptions above. If you've got
any specific questions about those, feel free to ask me directly.
> dd32 would you be able to review the .org side of things and confirm the
purpose of any field above that was unclear, and share any additional
fields that could potentially be returned?
I'm not sure how I can help here really, the APIs aren't set in stone and
there's always the possibility of new fields being added, whether or not
core uses them is the important bit. Most of these API's always return all
the data they have though, so this is probably all right at the present
point.
The main field I see missing above is `autoupdate` for the plugins/themes
endpoint, which can be set to `true` when a forced-push is available for
the plugin/theme. However, there's also #53333 which shows where it
could be expanded upon (and where a production API is returning data that
WordPress currently isn't using)
--
Ticket URL: <https://core.trac.wordpress.org/ticket/51126#comment:23>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list