Support MSC3757: Restricting who can overwrite a state event#17513
Support MSC3757: Restricting who can overwrite a state event#17513sandhose merged 29 commits intoelement-hq:release-v1.116from
Conversation
Restricting who can overwrite a state event
Support v9 because that is what the MSC says should be supported. Keep supporting v10 because it is the current default room version. Also support v11 because it is the latest room version.
|
The new & edited unit tests cover the MSC's auth rules. Since they all pass, this PR is ready for review. |
|
Can you expand the title of this PR? Each time I see a notification for it I wonder what MSC3757 is. |
hughns
left a comment
There was a problem hiding this comment.
@AndrewFerr as per conversation yesterday, I think the feature will need to be opt-in via configuration rather than enabled by default.
This is already opt-in by virtue of working only in rooms of a compatible version ( |
Also set errcode to M_BAD_JSON. Do this only for MSC3757 rooms.
sandhose
left a comment
There was a problem hiding this comment.
Looks good overall, this is mainly about code style
Support only the current default (10) and latest (11) room versions
sandhose
left a comment
There was a problem hiding this comment.
Very minor nitpicks, otherwise looks good to me!
|
Also note that this has Complement tests: matrix-org/complement#733 |
|
(Complement CI is expected to fail until matrix-org/complement#733 is merged.) |
to avoid confusion with a server administrator
|
Changed the base branch to release-v1.116 so that I can do another RC with it included |
Link to the MSC
Pull Request Checklist
EventStoretoEventWorkerStore.".code blocks.(run the linters)