For scalability. They don't need user-specific access, and we'll be hitting them quite a lot from client-side code.
Description
Description
Details
Details
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Open | None | T303353 Adjust system design to avoid significant performance bottlenecks | |||
In Progress | Jdforrester-WMF | T274269 Switch wikilambda_fetch/wikilambdaload_zobjects from Action API to REST API | |||
Resolved | gengh | T273127 Define and implement new API action to replace the internal use of wikilambda-fetch |
Event Timeline
Comment Actions
Change #1018807 had a related patch set uploaded (by Jforrester; author: Jforrester):
[mediawiki/extensions/WikiLambda@master] Introduce rest/wikifunctions/v0/fetch/<zids> REST API
Comment Actions
Change #1018808 had a related patch set uploaded (by Jforrester; author: Jforrester):
[mediawiki/extensions/WikiLambda@master] RESTAPI/FetchHandler: Add getDependencies feature from ApiQueryZObjects
Comment Actions
Change #1018807 merged by jenkins-bot:
[mediawiki/extensions/WikiLambda@master] Introduce rest/wikifunctions/v0/fetch/<zids> REST API