Spell out the state algorithm for createRoom
Fixes https://matrix.org/jira/browse/SPEC-429. Synapse currently follows the specified ordering, but does *not* give the specified error when the state is invalid (instead it creates the room anyway but gives a 403 M_FORBIDDEN). Still, I don't think that should be a real problem for any real clients, and nothing would break if we changed this in synapse, so it might as well go in the spec anyway.
This commit is contained in:
parent
c0490f2db2
commit
2370a4c970
3 changed files with 41 additions and 6 deletions
|
@ -123,7 +123,10 @@ Some requests have unique error codes:
|
|||
Encountered when trying to register a user ID which is not valid.
|
||||
|
||||
:``M_ROOM_IN_USE``:
|
||||
Encountered when trying to create a room which has been taken.
|
||||
Sent when the room alias given to the ``createRoom`` API is already in use.
|
||||
|
||||
:``M_INVALID_ROOM_STATE``:
|
||||
Sent when the intial state given to the ``createRoom`` API is invalid.
|
||||
|
||||
:``M_BAD_PAGINATION``:
|
||||
Encountered when specifying bad pagination query parameters.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue