wholetrans/docs-matrix-spec
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Correctly nest the capabilities response object

Browse source 
Everything is contained in a "capabilities" property, which is not represented by the schema. The example was correct.
This commit is contained in:
Travis Ralston 2019-02-11 20:31:48 -07:00
parent 3e06473305
commit d31d2f5e57
2 changed files with 37 additions and 32 deletions
Download patch file Download diff file Expand all files Collapse all files

6
api/client-server/capabilities.yaml
View file

@ -62,11 +62,15 @@ paths:
schema: schema:
type: object type: object
required: ["capabilities"] required: ["capabilities"]
additionalProperties: properties:
capabilities:
type: object type: object
title: Capabilities
description: |- description: |-
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:
type: object
properties: properties:
"m.change_password": "m.change_password":
type: object type: object

1
changelogs/client_server/newsfragments/1879.feature Normal file
View file

@ -0,0 +1 @@
Support optional features by having clients query for capabilities.