Additional keys in GET /capabilities don't have to be objects (#1945)
This commit is contained in:
parent
6d088e03a1
commit
75e77b96ff
2 changed files with 4 additions and 1 deletions
|
@ -0,0 +1 @@
|
||||||
|
Additional keys in `GET /capabilities` don't have to be objects.
|
|
@ -43,7 +43,9 @@ paths:
|
||||||
The custom capabilities the server supports, using the
|
The custom capabilities the server supports, using the
|
||||||
Java package naming convention.
|
Java package naming convention.
|
||||||
additionalProperties:
|
additionalProperties:
|
||||||
type: object
|
description: |-
|
||||||
|
Application-dependent keys using the
|
||||||
|
[Common Namespaced Identifier Grammar](/appendices/#common-namespaced-identifier-grammar).
|
||||||
properties:
|
properties:
|
||||||
m.change_password:
|
m.change_password:
|
||||||
$ref: '#/components/schemas/booleanCapability'
|
$ref: '#/components/schemas/booleanCapability'
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue