Extensions should be able to define REST modules (rather than just individual endpoints) using the RestModules key in their extension.json. Entries under the RestModules key refer to module definition files (T366837) in the extension's directory.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Stalled | None | T324931 Clean up open RESTBase related tickets | |||
| Open | None | T262315 <CORE TECHNOLOGY> API Migration & RESTBase Sunset | |||
| Resolved | Jgiannelos | T344944 Move Parsoid endpoints out of RESTBase | |||
| In Progress | None | T374135 Migrate RESTbase page content endpoints | |||
| Open | MSantos | T334238 Create deprecation plan for public parsoid endpoints | |||
| In Progress | daniel | T366835 REST: API modularization and versioning (tracking) | |||
| Duplicate | None | T366838 Allow extensions to define REST modules | |||
| Resolved | daniel | T366837 REST: Introduce module definition files | |||
| Resolved | daniel | T362480 Introduces support for modules into the REST API framework | |||
| Resolved | daniel | T365753 REST: expose a machine readable directory of available API modules | |||
| Resolved | daniel | T365755 REST: make module definition files compatible with OpenAPI specs |
Event Timeline
Comment Actions
Change #1031974 had a related patch set uploaded (by Daniel Kinzler; author: Daniel Kinzler):
[mediawiki/core@master] REST: Add support for RestModules to extension.json