[wp-meta] [Making WordPress.org] #2112: Review API endpoints

Making WordPress.org noreply at wordpress.org
Mon Dec 26 10:01:50 UTC 2016

#2112: Review API endpoints
 Reporter:  tellyworth        |       Owner:  tellyworth
     Type:  task              |      Status:  assigned
 Priority:  normal            |   Milestone:  Plugin Directory v3.0
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |

Comment (by obenland):

 Replying to [comment:11 dd32]:
 > If [FAQs are] actually being display filtered somewhere, we could also
 just skip adding any wrapping elements.

 True. Here too we could just return the raw data and let apps decide on
 how they'll display it for themselves.

 > I fully expect to add an extra field to indicate that the client wants
 the semantic markup and handle it nicely within WordPress too, down the
 line, leaving this just as BC stuff.

 I wonder if we should designate the `/plugins/v1` endpoints for core and
 the `/wp/v2` endpoints (with raw data) for apps?

 > > Could we use DATE_ATOM instead of custom date formats for all date-
 related information in the API?
 > [If] you can point to the field you're referencing, and why, I might be
 able to suggest more details.

 Specifically the `last_updated` field. I tried dumping it into `moment.js`
 but it complained about the non-ISO format. I was able to mitigate it by
 passing a parsing format, but standardizing it on ISO 6801 could make
 sense for more than just that.

Ticket URL: <https://meta.trac.wordpress.org/ticket/2112#comment:12>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

More information about the wp-meta mailing list