Fix federated leaves dropping the reason #789
No reviewers
Labels
No labels
Bug
Cherry-picking
Database
Dependencies
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/Federation
Matrix/MSC
Matrix/Media
Meta
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
Wont fix
old/ci/cd
old/rust
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: continuwuation/continuwuity#789
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "nex/fix-768"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fixes #768
this small change fixes the issue where leaving a room over federation drops the client-included reason, bringing behavior in line of that of synapse and other implementations.
Looks good! I was a bit surprised that there's no typing on the leave event, but I guess it is more flexible for other servers.
The v1 leave is documented in the spec as being a bit flimsy, v2 is meant to be more "consistent", but that's out of scope for this PR
b8bfd1c3fa
to41cf118a24