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 <[email protected]>
matrix-org · May 30, 2022 · 9d07c9a · 9d07c9a
1 parent 25a9dcf
commit 9d07c9a
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 2 deletions.
diff --git a/changelogs/client_server/newsfragments/1097.clarification b/changelogs/client_server/newsfragments/1097.clarification
@@ -0,0 +1 @@
+Adjust the data types of the Spaces Hierarchy query parameters.
diff --git a/data/api/client-server/space_hierarchy.yaml b/data/api/client-server/space_hierarchy.yaml
@@ -58,7 +58,7 @@ paths:
             contents.
           x-example: true
         - in: query
-          type: number
+          type: integer
           name: limit
           description: |-
             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.
           x-example: 20
         - in: query
-          type: number
+          type: integer
           name: max_depth
           description: |-
             Optional limit for how far to go into the space. Must be a non-negative integer.
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1 @@
		Adjust the data types of the Spaces Hierarchy query parameters.