fix: spaces hierarchy paramater types (#1097)
* fix: spaces hierarchy paramater types - changed `limit` parameter type to integer - changed `query` parameter type to integer A floating number does not make any sense here. Also, at least Synapse does not allow floating point numbers in here. Signed-off-by: TheOneWithTheBraid <the-one@with-the-braid.cf> * Update changelogs/client_server/newsfragments/1097.clarification Co-authored-by: Travis Ralston <travpc@gmail.com>
This commit is contained in:
parent
10bd1b5038
commit
31304300f5
2 changed files with 3 additions and 2 deletions
|
@ -0,0 +1 @@
|
||||||
|
Fix various typos throughout the specification.
|
|
@ -58,7 +58,7 @@ paths:
|
||||||
contents.
|
contents.
|
||||||
x-example: true
|
x-example: true
|
||||||
- in: query
|
- in: query
|
||||||
type: number
|
type: integer
|
||||||
name: limit
|
name: limit
|
||||||
description: |-
|
description: |-
|
||||||
Optional limit for the maximum number of rooms to include per response. Must be an integer
|
Optional limit for the maximum number of rooms to include per response. Must be an integer
|
||||||
|
@ -67,7 +67,7 @@ paths:
|
||||||
Servers should apply a default value, and impose a maximum value to avoid resource exhaustion.
|
Servers should apply a default value, and impose a maximum value to avoid resource exhaustion.
|
||||||
x-example: 20
|
x-example: 20
|
||||||
- in: query
|
- in: query
|
||||||
type: number
|
type: integer
|
||||||
name: max_depth
|
name: max_depth
|
||||||
description: |-
|
description: |-
|
||||||
Optional limit for how far to go into the space. Must be a non-negative integer.
|
Optional limit for how far to go into the space. Must be a non-negative integer.
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue