Files
synapse/tests
Jason Robinson 84946f8d30 Adjust MSC4429 profile updates over legacy removed fields in response
Due to MSC4429 being in flux and clients having implemented field removals early, the previously merged implementation pushed field removals by setting the value to `null`. The MSC will require delivering the fields in a separate `removed_profile_fields` key as `None` is a valid field value, see https://github.com/matrix-org/matrix-spec-proposals/pull/4429#discussion_r3512513534

Thus, as we moved storing field deletes to `ProfileUpdateAction.DELETE`, we need to adjust the legacy sync to properly identify deletes. At the same time have implemented the new `removed_profile_fields` key, so we have it ready for simplifying the legacy sync response in the future.
2026-08-18 15:13:27 +03:00
..
2026-06-02 11:05:38 +01:00