aboutsummaryrefslogtreecommitdiffstats
path: root/includes/Rest/Handler/Schema
Commit message (Collapse)AuthorAgeFilesLines
* Merge "REST: Make OpenAPI spec info strings translatable"jenkins-bot2025-03-241-2/+2
|\
| * REST: Make OpenAPI spec info strings translatablebpirkle2025-03-211-2/+2
| | | | | | | | | | | | | | | | | | OpenAPI specs include an "info" section that includes strings such as "title" and "description" that are intended to be human-readable. Make all such strings translatable. Bug: T385855 Change-Id: I15285be6d196c0e7fd7e922f23058d7c09b6b31a
* | Translate response body property descriptions for remaining endpointsfrankie2025-03-2010-107/+107
|/ | | | | | | Extending the work began in T3847447, in a continued effort to auto-generate translatable messages in OpenAPI specs, refactor schemas for content.v1 endpoints to accept translatable strings. Bug: T384750 Change-Id: I95b51021babbed1800ed53ee0066cbe83b3b7535
* Translate response body property descriptions for 'content.v1' endpointsfrankie2025-02-257-124/+124
| | | | | | | As part of the effort to auto generate translatable messages in OpenAPI specs, refactor schemas for content.v1 endpoints to accept translatable strings. Bug: T384747 Change-Id: I728f0932a770eba56c2ad8e26c74f88fa266a1f9
* Merge "REST: Search: Validate responses against response schemas in tests"jenkins-bot2025-01-241-0/+1
|\
| * REST: Search: Validate responses against response schemas in testsAtieno2025-01-221-0/+1
| | | | | | | | | | Bug: T382455 Change-Id: Ia10c5226dad5162b35c4e9b139876de735cf4a1b
* | REST: Content/v1: Validate responses against response schemas in testsAtieno2025-01-154-11/+98
|/ | | | | Bug: T376607 Change-Id: I837b0a8471b8a2c8675d33852406d3ba4ce4ae05
* REST: Add remaining response schemas for core endpointsbpirkle2024-12-208-17/+393
| | | | | Bug: T382264 Change-Id: Iec5f168629622a0094cbbaeff4f143d1c39e9bb6
* REST: Allow response body properties to have translatable descriptionsbpirkle2024-12-171-2/+2
| | | | | | | | | | | | | In https://gerrit.wikimedia.org/r/c/mediawiki/core/+/1078506 we added the ability to specify path/query parameter descriptions as MessageValue objects to expose them in a translatable way in OpenAPI specs. Make the same possible for response body parameters. Caveat: only schema and top-level property descriptions are translated. Description translation in nested objects is not supported in this patch. Bug: T379706 Change-Id: I68215ad55f2e8b2fec4315516e874192faba6595
* REST: JSON schema definitions for additional response bodiesWendy Quarshie2024-12-039-17/+709
| | | | | | Bug: T376603 Depends-On: I4193b9be4516717c7ce423131370a7d0b6ea8962 Change-Id: Ic2d9471ad446eb5f9d5e7072f1ef93f7196a20f8
* Define and store MediaWiki REST API ‘page’ endpoint responses as JSON ↵Wendy Quarshie2024-11-072-0/+95
| | | | | | | schemas Bug: T375530 Change-Id: I4193b9be4516717c7ce423131370a7d0b6ea8962
* REST: Allow specifying response body schemas in json filesbpirkle2024-10-101-0/+87
Previously, response body schemas could be specified by handlers as php associative arrays, that were included in the final OpenApi spec. This mixed the schemas with code, and required developers to deal with specs in multiple formats. Instead, allow specs to be specified in JSON format, in separate files. In addition to keeping schemas in JSON, this gives each schame its own git history. Bug: T376290 Change-Id: Ic27f422df0ab12a3a0b1cbce79eb0be30f7b7815
generated by cgit v1.2.3 (git 2.25.1) at 2025-04-26 11:44:07 +0000