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.

Sign up for GitHub

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

Jump to bottom

Consider adding options to selectively transfer state on room version upgrade #454

Open
turt2live opened this issue Mar 26, 2019 · 1 comment
Open

Consider adding options to selectively transfer state on room version upgrade #454

turt2live opened this issue Mar 26, 2019 · 1 comment
Labels
A-Client-Server Issues affecting the CS API enhancement A suggestion for a relatively simple improvement to the protocol

Comments

@turt2live
Copy link
Member

Something like POST /upgrade with {not_types:[m.room.name]} or something
@turt2live turt2live added enhancement A suggestion for a relatively simple improvement to the protocol A-Client-Server Issues affecting the CS API labels Mar 26, 2019
@dkasak dkasak changed the title Consider adding options to selectively transfer state on upgrade Consider adding options to selectively transfer state on room version upgrade Sep 29, 2021
@richvdh richvdh transferred this issue from matrix-org/matrix-spec-proposals Mar 1, 2022
@ara4n ara4n mentioned this issue Mar 1, 2022
Open
17 tasks
@ShadowJonathan
Copy link
Contributor

2c: A types field instead of a not_types field.

#1324 mentions that the spec currently 'recommends' types to be copied over, but this could be greatly helped by shifting the responsibility to clients instead to enumerate all the types to be copied over, giving them greater control.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-Client-Server Issues affecting the CS API enhancement A suggestion for a relatively simple improvement to the protocol
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@turt2live @ShadowJonathan