Upgrading a room can orphan it from its space #460
Labels
A-Room-Upgrades
A-Spaces
Spaces, groups, communities
O-Uncommon
Most users are unlikely to come across this or unexpected workflow
S-Major
Severely degrades major functionality or product features, with no satisfactory workaround
T-Defect
X-Spec-Changes
Steps to reproduce
For context, while this is an uncommon scenario, it's already happened in the Element Corp. space.
Outcome
What did you expect?
User C should see Room B listed as a child of the space.
What happened instead?
To User C, Room B appears as an orphaned room, since the space actually only lists Room A as a child, and User C has no way to know about the upgrade.
Well, that's not entirely true. User C could find out about the upgrade by looking at the room creation event. But if the room were upgraded twice rather than once, this would still not be enough information to connect the upgraded room back to Room A.
I'm not sure how this could be resolved. Perhaps spec changes?
Operating system
NixOS unstable
Browser information
Firefox 97.0.1
URL for webapp
develop.element.io
Application version
Element version: 95de708f4ee7-react-1a6134e441ba-js-53aa34fba57c Olm version: 3.2.8
Homeserver
Synapse 1.52.0
Will you send logs?
No
The text was updated successfully, but these errors were encountered: