Change Details

The Wikimedia OpenAPI Linter requires endpoints to be grouped by [tags](https://spec.openapis.org/oas/v3.0.html#tag-object), so the MediaWiki REST API OpenAPI docs should support defining tags and assigning them to individual paths. Both the tag `name` and `description` should be translatable. Example: ``` ... "tags": [ { "name": "Math" } ], ... "paths": { "/media/math/check/{type}": { "post": { "tags": [ "Math" ], ... ``` The OpenAPI spec also support a `description` field and an `externalDocs` object for tags. In my opinion, these would be nice to have but are lower priority and should be considered outside the scope of this task.

The Wikimedia OpenAPI Linter requires endpoints to be grouped by [tags](https://spec.openapis.org/oas/v3.0.html#tag-object), so the MediaWiki REST API OpenAPI docs should support defining tags and assigning them to individual paths. Both the tag `name` and `description` should be translatable. Example: ``` ... "tags": [ { "name": "Math" } ], ... "paths": { "/media/math/check/{type}": { "post": { "tags": [ "Math" ], ... ``` The OpenAPI spec also supports a `description` field and an `externalDocs` object for tags. In my opinion, these would be nice to have but are lower priority and should be considered outside the scope of this task.

The Wikimedia OpenAPI Linter requires endpoints to be grouped by [tags](https://spec.openapis.org/oas/v3.0.html#tag-object), so the MediaWiki REST API OpenAPI docs should support defining tags and assigning them to individual paths. Both the tag `name` and `description` should be translatable. Example: ``` ... "tags": [ { "name": "Math" } ], ... "paths": { "/media/math/check/{type}": { "post": { "tags": [ "Math" ], ... ``` The OpenAPI spec also supports a `description` field and an `externalDocs` object for tags. In my opinion, these would be nice to have but are lower priority and should be considered outside the scope of this task.