mirror of
https://github.com/element-hq/synapse.git
synced 2026-11-04 11:17:51 +00:00
Jason Robinson
2ff51d3c7f
As per https://github.com/element-hq/synapse/issues/20419 this change broke Element Web clearing user status, which basically means the client is stuck with any status, and users cannot set a new one. EW should move to use DELETE to clear user status, but until then we should ensure the feature is not broken on existing clients in the wild. Should we set a clear deprecation time for rejecting nulls? There might be other clients using profile fields and doing PUT to clear the field. Discussed in [`#element-backend-internal:matrix.org`](https://matrix.to/#/!SGNQGPGUwtcPBUotTL:matrix.org/$b7zid3lLGdFDC8pwy1IvSPv3zl9y1fXEpnnBte9vcQU?via=jki.re&via=element.io&via=matrix.org) [[1]](https://matrix.to/#/!SGNQGPGUwtcPBUotTL:matrix.org/$jTEcHlDBIvKRAKtV-ESXabkPkLia9B7C4JQVkoOxzj0?via=jki.re&via=element.io&via=matrix.org) Reverts a part of https://github.com/element-hq/synapse/pull/20153 by only rejecting null fields when the profile update stream is configured (ie user status requirement). Future work to unrevert tracked by https://github.com/element-hq/synapse/issues/20424