[wp-meta] [Making WordPress.org] #7057: Make / plugin API for closed plugins that are no longer available

Making WordPress.org noreply at wordpress.org
Thu Oct 26 18:14:25 UTC 2023


#7057: Make / plugin API for closed plugins that are no longer available
--------------------------------------+---------------------
 Reporter:  ramon fincken             |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  API                       |  Resolution:
 Keywords:  needs-patch dev-feedback  |
--------------------------------------+---------------------

Comment (by eclev91):

 @dd32 What has historically been the process by which that API is updated
 and versioned?

 I assume the first steps here would be to outline what changes would be
 required to the result schema. At minimum, I think adding a `status` field
 that is simply text would be a good start. But that could also be an array
 including some kind of status shorthand/slug, a human-readable message,
 and an effective date if applicable.

 Without more information about how the back end of the plugin repository
 and existing API work, it's hard to propose anything firmer, and nothing
 on which to base a PR.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/7057#comment:7>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list