Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Merged
merged 2 commits into from
Sep 11, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Additional keys in `GET /capabilities` don't have to be objects.
4 changes: 3 additions & 1 deletion data/api/client-server/capabilities.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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'
Expand Down