|
|
|
|
@ -20,17 +20,21 @@ New `errcode` would be introduced into the error body of a response
|
|
|
|
|
|
|
|
|
|
`M_ALREADY_JOINED` would be fired when a membership action fails when the authenticated user
|
|
|
|
|
is already joined to the room.
|
|
|
|
|
|
|
|
|
|
This would cover endpoints:
|
|
|
|
|
- [POST /_matrix/client/v3/rooms/{roomId}/invite](https://spec.matrix.org/v1.3/client-server-api/#post_matrixclientv3roomsroomidinvite)
|
|
|
|
|
- [POST /_matrix/client/v3/rooms/knock/{roomIdOrAlias}](https://spec.matrix.org/v1.3/client-server-api/#post_matrixclientv3knockroomidoralias)
|
|
|
|
|
- [PUT /_matrix/client/v3/rooms/{roomId}/state/{eventType}/{stateKey}](https://spec.matrix.org/v1.3/client-server-api/#put_matrixclientv3roomsroomidstateeventtypestatekey)
|
|
|
|
|
|
|
|
|
|
Note that it would not cover endpoints where trying to join a room when the
|
|
|
|
|
user is already joined would no-op, like `POST /_matrix/client/v3/join/{roomIdOrAlias}`.
|
|
|
|
|
|
|
|
|
|
`M_INSUFFICIENT_POWER` would be when the authenticated user does not have the specific required power level to
|
|
|
|
|
perform an action in the room.
|
|
|
|
|
|
|
|
|
|
`M_NOT_JOINED` would be when the authenticated user is not joined to a room, but attempts to perform
|
|
|
|
|
an action in it.
|
|
|
|
|
|
|
|
|
|
Both errcodes would cover endpoints:
|
|
|
|
|
- [POST /_matrix/client/v3/rooms/{roomId}/invite](https://spec.matrix.org/v1.3/client-server-api/#post_matrixclientv3roomsroomidinvite)
|
|
|
|
|
- [POST /_matrix/client/v3/rooms/knock/{roomIdOrAlias}](https://spec.matrix.org/v1.3/client-server-api/#post_matrixclientv3knockroomidoralias)
|
|
|
|
|
|