Skip to content

Commit 2439ceb

Browse files
committed
add proposal xxxx-copy-room-type-on-upgrade.md
Signed-off-by: Aminda Suomalainen <suomalainen+git@mikaela.info>
1 parent 0e9020a commit 2439ceb

File tree

1 file changed

+36
-0
lines changed

1 file changed

+36
-0
lines changed
Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
# MSCXXXX: Copy room type on upgrade.
2+
3+
There can never be enough templates in the world, and MSCs shouldn't be any different. The level
4+
of detail expected of proposals can be unclear - this is what this example proposal (which doubles
5+
as a template itself) aims to resolve.
6+
7+
Unless the room upgrade API specifies that room type must be copied over, clients cannot rely on
8+
rooms staying the same type leading to trouble.
9+
10+
11+
## Proposal
12+
13+
This MSC proposes that the room upgade API MUST copy the room type over to the new room. Otherwise
14+
clients cannot trust that to happen and Spaces or MSC3588 Story rooms may incorrectly become normal
15+
rooms breaking user-experience.
16+
17+
18+
## Potential issues
19+
20+
Non-applicable.
21+
22+
## Alternatives
23+
24+
Non-applicable.
25+
26+
## Security considerations
27+
28+
Non-applicable.
29+
30+
## Unstable prefix
31+
32+
Non-applicable.
33+
34+
## Dependencies
35+
36+
Non-applicable.

0 commit comments

Comments
 (0)