You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the new property with_relations has been renamed with_rel_types (to prevent us from introducing a new term ("relations") to refer to event relationships). Only the stable name is changed, we keep the existing unstable one.
we introduced a catch-all "*" value, which if found in the list means "any relation type"
This implementation is lacking a way to keep watch for incoming events that match the redaction criteria after the redaction request finishes, that'll come in a separate PR.
We have to decide if the backend team can work on this border use case by provided an additional PR. If not, we should remove this part from the MSC (details)
The text was updated successfully, but these errors were encountered:
This issue has been migrated from #15687.
Description:
Since MSC3912 has been implemented by matrix-org/synapse#14260, we introduced 2 changes into the MSC for which we need to update this implementation :
with_relations
has been renamedwith_rel_types
(to prevent us from introducing a new term ("relations") to refer to event relationships). Only the stable name is changed, we keep the existing unstable one."*"
value, which if found in the list means "any relation type"There is one stuff missing:
The first Synapse PR (matrix-org/synapse#14260) says:
We have to decide if the backend team can work on this border use case by provided an additional PR. If not, we should remove this part from the MSC (details)
The text was updated successfully, but these errors were encountered: