Page MenuHomePhabricator

Spike: Check book ref. compatibility with the REST API endpoint
Closed, ResolvedPublic8 Estimated Story Points

Description

There is a REST API endpoint at https://en.wikipedia.org/api/rest_v1/#/Page%20content/getContent-references that extracts references from a page (either from the current or an old revision). This was implemented for the mobile skin and/or mobile apps.

To do:

  • Make sure our extension does not break this API.
  • We might need to expand this API, so users can see which references belong to each other (which is a sub of which) in the API's JSON response. This might need consultation with the WMF team originally responsible for the implementation.

Event Timeline

awight renamed this task from Check book ref. compatibility with the REST API endpoint to Spike: Check book ref. compatibility with the REST API endpoint.Nov 12 2019, 12:48 PM
awight moved this task from Backlog to Default version backlog on the Cite-Extends board.
thiemowmde set the point value for this task to 8.Nov 26 2019, 12:36 PM

In todays meeting with WMF it was said the RESTBase stuff will not be supported any more, and some day be removed. It is already not used any more in the MobileFrontend codebase (which is why I removed this from T239228).

In todays meeting with WMF it was said the RESTBase stuff will not be supported any more, and some day be removed. It is already not used any more in the MobileFrontend codebase (which is why I removed this from T239228).

Due to that comment I will mark this ticket invalid now. There seem to be no need for us to support compatibility here.

I agree we don't need to make the extends feature available via the REST API. But we need to make sure our changes do not break the API. As far as I remember we checked this already. To be sure I checked again:

It succeeds and returns all 4 references from the page, just as 4 independent top-level references. The last one shows "S.128-129", for example.

thiemowmde changed the task status from Declined to Resolved.Jan 21 2020, 4:11 PM