| Commit message (Collapse) | Author | Files | Lines |
|
Tests were broken due to an API changing. The code used in Synapse
proper should be compatible with both versions already.
|
|
This applies even if the feature is disabled at the server level with `allow_per_room_profiles`.
The server notice not being a real user it doesn't have an user profile.
|
|
We don't use newsfiles for DINUM releases anyways, so a CI requirement for them
does not make sense.
|
|
|
|
|
|
creating a room (#68)
The createRoom flow in DINUM's Synapse (through the AccessRules module which has hooks for all of this) already rejects a power levels content dict if it doesn't have high enough power levels to satisfy DINUM's [requirements](https://github.com/matrix-org/synapse-dinsic/blob/ac50ed353b5fdbdf9f853be0d94b6fccaf33973e/synapse/third_party_rules/access_rules.py#L233-L252).
This PR ensures that any keys that aren't provided are replaced with the defaults, instead of just assuming the whole dict was correct (and thus those keys were set to mainline Synapse's default instead).
|
|
|
|
|