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
Since MSC3912 has been implemented by #7988, we introduced 2 changes into the MSC for which we need to update this implementation :
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"
We should apply changes in the SDK only for the first point. The SDK seems already support the second point.
This second point should be taken into account mainly in a moderation tool where the client may not be aware of the relation types associated with an event. I'm not sure there is already a use case at the application level
Are you willing to provide a PR?
Yes
The text was updated successfully, but these errors were encountered:
giomfo
added
the
T-Enhancement
New features, changes in functionality, performance boosts, user-facing improvements
label
May 29, 2023
Description:
Since MSC3912 has been implemented by #7988, 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"We should apply changes in the SDK only for the first point. The SDK seems already support the second point.
This second point should be taken into account mainly in a moderation tool where the client may not be aware of the relation types associated with an event. I'm not sure there is already a use case at the application level
Are you willing to provide a PR?
Yes
The text was updated successfully, but these errors were encountered: