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>
This commit is contained in:
TheOneWithTheBraid 2022-05-30 07:11:36 +02:00
parent 25a9dcfd3c
commit 9d07c9a014
2 changed files with 3 additions and 2 deletions

View file

@ -0,0 +1 @@
Adjust the data types of the Spaces Hierarchy query parameters.

View file

@ -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.