For this to work, we'll have to implement i10n in the code that generates the spec, e.g. jsonBodyValidator::getOpenAPISpec().
Compare the discusstion at https://github.com/OAI/OpenAPI-Specification/issues/274
Also, we'll want to think about how exactly to do that. Do we just change the descriptions, or do we add different keys, like this library does? https://www.npmjs.com/package/swagger-i18n-extensio
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Stalled | None | T324931 Clean up open RESTBase related tickets | |||
| In Progress | None | T262315 <CORE TECHNOLOGY> API Migration & RESTBase Sunset | |||
| Open | None | T353157 Port CampaignEvents REST API documentation to swagger | |||
| In Progress | daniel | T362006 Provide a Swagger-UI for exploring the core REST API | |||
| Resolved | BPirkle | T323786 REST framework: Add support for outputting an OpenAPI (swagger) spec | |||
| Open | None | T350161 Cleanup: REST framework: Add support for outputting an OpenAPI (swagger) spec | |||
| Open | None | T352183 Support i18n for JSON body descriptions |
Hi @Atieno, can you please associate one or more active project tags with this task (via the Add Action... → Change Project Tags dropdown)? That will allow to see a task when looking at project workboards or searching for tasks in certain projects, and get notified about a task when watching a related project tag. Thanks!