- spec: https://www.mediawiki.org/wiki/Parsoid/API
- current users: https://www.mediawiki.org/wiki/Parsoid/Users
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • GWicke | T88319 Replicate Parsoid v1 API functionality in RESTBase | |||
| Resolved | • GWicke | T75955 RESTBase / Parsoid integration - waiting for parsoid deploy | |||
| Resolved | • Jdouglas | T88456 On-demand generation of HTML and data-parsoid | |||
| Resolved | • GWicke | T88457 html2wt conversion support | |||
| Resolved | • GWicke | T88588 Formalize the RESTBase v1 specification | |||
| Resolved | Arlolra | T89411 Parsoid v2 API selser might not be working correctly |
Event Timeline
Comment Actions
Are we talking here about encapsulating Parsoid's API following RESTBase's logic and hierarchy or pure copying/proxying (with the same URI structure as Parsoid's)?
Comment Actions
@mobrovac, we are talking about providing *the same functionality*, in an API that makes sense as a wider content API (so not necessarily the same as the Parsoid API). We already do this for the most part, there are only some minor bits like support for the bodyOnly flag missing.
Comment Actions
Current spec: https://github.com/wikimedia/restbase/blob/master/specs/mediawiki/v1/content.yaml
The main bit of missing functionality is the bodyOnly flag in wt2html transformations (body in the v1 API), which lets clients retrieve only body.innerHTML.
Comment Actions
bodyOnly is now implemented.
The functionality is now fairly complete. HTML to wikitext conversion with selective serialization is still blocked on T89411, but I think otherwise we are in good shape.