From 2439ceb2824bd0d53b79310fb78d5467d8b1de7a Mon Sep 17 00:00:00 2001 From: Aminda Suomalainen Date: Wed, 18 May 2022 16:47:15 +0300 Subject: [PATCH] add proposal xxxx-copy-room-type-on-upgrade.md Signed-off-by: Aminda Suomalainen --- proposals/xxxx-copy-room-type-on-upgrade.md | 36 +++++++++++++++++++++ 1 file changed, 36 insertions(+) create mode 100644 proposals/xxxx-copy-room-type-on-upgrade.md diff --git a/proposals/xxxx-copy-room-type-on-upgrade.md b/proposals/xxxx-copy-room-type-on-upgrade.md new file mode 100644 index 00000000000..0365e7bcb29 --- /dev/null +++ b/proposals/xxxx-copy-room-type-on-upgrade.md @@ -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.