Skip to content

Commit

Permalink
add proposal xxxx-copy-room-type-on-upgrade.md
Browse files Browse the repository at this point in the history
Signed-off-by: Aminda Suomalainen <suomalainen+git@mikaela.info>
  • Loading branch information
Mikaela committed May 18, 2022
1 parent 0e9020a commit 2439ceb
Showing 1 changed file with 36 additions and 0 deletions.
36 changes: 36 additions & 0 deletions proposals/xxxx-copy-room-type-on-upgrade.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
# MSCXXXX: Copy room type on upgrade.

There can never be enough templates in the world, and MSCs shouldn't be any different. The level
of detail expected of proposals can be unclear - this is what this example proposal (which doubles
as a template itself) aims to resolve.

Unless the room upgrade API specifies that room type must be copied over, clients cannot rely on
rooms staying the same type leading to trouble.


## Proposal

This MSC proposes that the room upgade API MUST copy the room type over to the new room. Otherwise
clients cannot trust that to happen and Spaces or MSC3588 Story rooms may incorrectly become normal
rooms breaking user-experience.


## Potential issues

Non-applicable.

## Alternatives

Non-applicable.

## Security considerations

Non-applicable.

## Unstable prefix

Non-applicable.

## Dependencies

Non-applicable.

0 comments on commit 2439ceb

Please sign in to comment.