Cleanup additionalProperties usage

In capabilities.yaml, additional properties are more likely to be
strings (but can also be objects); in cross_signing_key.yaml,
the parameter documentation already restricts the number of properties.
This commit is contained in:
Alexey Rusakov 2023-02-28 14:53:36 +01:00
parent 77d0f20226
commit 260107941d
2 changed files with 3 additions and 2 deletions

View file

@ -69,8 +69,7 @@ paths:
description: |-
The custom capabilities the server supports, using the
Java package naming convention.
additionalProperties:
type: object
additionalProperties: true
properties:
"m.change_password":
type: object

View file

@ -35,6 +35,8 @@ properties:
The public key. The object must have exactly one property, whose name is
in the form `<algorithm>:<unpadded_base64_public_key>`, and whose value
is the unpadded base64 public key.
minProperties: 1
maxProperties: 1
example:
"ed25519:alice+base64+public+key": "alice+base64+public+key"
signatures: