daniel 602f0ab595 REST: add restbase compat mode for some endpoints ... In order to replace the /api/rest_v1/page/title/{title} endpoints, we need to have something in MediaWiki that generates a compatible responser. The v1/page/{title}/bare and v1/revision/{id}/bare endpoints are functionally equivalent, so the easiest approach seemed to be to add a compatibility mode to them. The compatibility mode is triggered using the x-restbase-compat header, which can be set via the gateway when routing the request from /api/rest_v1/page/title/. Bug: T374136 Change-Id: I4af7ff5325660ae30faebb24753b9dc1c3acb2b3		2024-09-15 16:41:21 -05:00
..
content.v1	REST: add restbase compat mode for some endpoints	2024-09-15 16:41:21 -05:00
CreationLegacy.js	Add content.v1 REST module with relevant content endpoints	2024-08-07 16:51:09 -05:00
PageHistory.js	api-testing/REST/PageHistory.js: update tests for temp account	2024-07-11 09:27:21 +00:00
PageLegacy.js	Add content.v1 REST module with relevant content endpoints	2024-08-07 16:51:09 -05:00
RevisionCompare.js	Add content.v1 REST module with relevant content endpoints	2024-08-07 16:51:09 -05:00
RevisionLegacy.js	Add content.v1 REST module with relevant content endpoints	2024-08-07 16:51:09 -05:00
Search.js	ESLint: Enforce prefer-arrow-callback and autofix	2024-06-11 19:03:54 +01:00
Swagger.js	REST: Generate request body specs from param settings.	2024-07-10 20:23:56 +02:00
Transform.js	ESLint: Enforce prefer-arrow-callback and autofix	2024-06-11 19:03:54 +01:00
UpdateLegacy.js	Add content.v1 REST module with relevant content endpoints	2024-08-07 16:51:09 -05:00