Additional keys in GET /capabilities don't have to be objects (#1945)

2024-09-11 13:51:27 +02:00 · 2024-09-11 13:51:27 +02:00 · 75e77b96ff
commit 75e77b96ff
parent 6d088e03a1
2 changed files with 4 additions and 1 deletions
--- a/changelogs/client_server/newsfragments/1945.clarification
+++ b/changelogs/client_server/newsfragments/1945.clarification
@ -0,0 +1 @@
+Additional keys in `GET /capabilities` don't have to be objects.
--- a/data/api/client-server/capabilities.yaml
+++ b/data/api/client-server/capabilities.yaml
@ -43,7 +43,9 @@ paths:
                      The custom capabilities the server supports, using the
                      Java package naming convention.
                    additionalProperties:
-                      type: object
+                      description: |-
+                        Application-dependent keys using the
+                        [Common Namespaced Identifier Grammar](/appendices/#common-namespaced-identifier-grammar).
                    properties:
                      m.change_password:
                        $ref: '#/components/schemas/booleanCapability'
				`@ -0,0 +1 @@`
				Additional keys in `GET /capabilities` don't have to be objects.