Reject r0, embrace v1

Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com>
pull/3822/head
Will Hunt 4 years ago committed by GitHub
parent a1de65f178
commit d59d05187a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

@ -30,7 +30,7 @@ Additionally, a server may respond with a `400` `M_UNKNOWN` to this endpoint for
signalling its unwillingess (or inability) to satisfy the request. signalling its unwillingess (or inability) to satisfy the request.
``` ```
GET /_matrix/client/r0/user/mutual_rooms/%40bob%3Aexample.com GET /_matrix/client/v1/user/mutual_rooms/%40bob%3Aexample.com
``` ```
```json ```json
@ -77,5 +77,5 @@ to request all state ahead of time.
The implementation MUST use `/_matrix/client/unstable/uk.half-shot.msc2666/user/mutual_rooms/{user_id}`. The implementation MUST use `/_matrix/client/unstable/uk.half-shot.msc2666/user/mutual_rooms/{user_id}`.
The /versions endpoint MUST include a new key in `unstable_features` with the name `uk.half-shot.msc2666.mutual_rooms`. The /versions endpoint MUST include a new key in `unstable_features` with the name `uk.half-shot.msc2666.mutual_rooms`.
If the value is false or the key is not present, clients MUST assume the feature is not available. If the value is false or the key is not present, clients MUST assume the feature is not available.
Once the MSC has been merged, clients should use `/_matrix/client/r0/user/mutual_rooms/{user_id}` Once the MSC has been merged, clients should use `/_matrix/client/v1/user/mutual_rooms/{user_id}`
and will no longer need to check for the `unstable_features` flag. and will no longer need to check for the `unstable_features` flag.

Loading…
Cancel
Save