Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Meta bug for edge cases that should be considered to make room upgrades transparent #456

Open
12 of 17 tasks
ara4n opened this issue Mar 27, 2019 · 7 comments
Open
12 of 17 tasks
Labels
A-Client-Server Issues affecting the CS API epic feature Suggestion for a significant extension which needs considerable consideration

Comments

@ara4n
Copy link
Member

ara4n commented Mar 27, 2019

At the least, we should ensure the spec reminds implementors to handle all these edge cases...

@turt2live turt2live added clarification An area where the expected behaviour is understood, but the spec could do with being more explicit feature Suggestion for a significant extension which needs considerable consideration epic A-Client-Server Issues affecting the CS API labels Mar 27, 2019
@richvdh
Copy link
Member

richvdh commented Mar 28, 2019

@richvdh
Copy link
Member

richvdh commented Apr 9, 2019

Arbitrary room state #454, #427

Neither #454 nor #427 appear to be "copy all state over by default", which is what I think you mean here?

@turt2live turt2live removed the clarification An area where the expected behaviour is understood, but the spec could do with being more explicit label May 25, 2019
@julianfoad
Copy link

@anoadragon453
Copy link
Member

Curious if these two issues are solved by client-side behaviour now, or if that's not considered the ideal end goal:

@Half-Shot
Copy link
Contributor

I have nothing specific to add here, other than a datapoint that we upgraded a lot of rooms within a space today and it was a very painful experience to copy state over. A lot of the bots I tend to use in EMS-land use room state for configuration, and it doesn't feel like the bots should be responsible for copying that state over.

@clokep
Copy link
Member

clokep commented Sep 28, 2021

matrix-org/synapse#10774 made upgrading a space possible, which seems like it should be mentioned somewhere here. 😄

@dkasak
Copy link
Member

dkasak commented Sep 29, 2021

Regarding carrying over arbitrary room state, there seemed to be some consensus that it was the way to go yesterday, but two points were raised:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Client-Server Issues affecting the CS API epic feature Suggestion for a significant extension which needs considerable consideration
Projects
None yet
Development

No branches or pull requests

8 participants