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
This in accordance with Matrix's new Global Versioning, which moves to per-endpoint versioning.
This way, new endpoint versions can easily be added (v4 under the related module, like above) and maintained, instead of having to be in fluid accordance to sub-revisions.
"The matrix version that ruma supports" can then be further granularized, and "old versions" supported much more easily.
It could also open up some form of "specify the matrix versions you want" via crate features, which then define/undefine specific endpoints/versions/features by macros.
Basically,
r0::sync::sync_events
->sync::sync_events::{v3, v4, ...}
This in accordance with Matrix's new Global Versioning, which moves to per-endpoint versioning.
This way, new endpoint versions can easily be added (
v4
under the related module, like above) and maintained, instead of having to be in fluid accordance to sub-revisions."The matrix version that ruma supports" can then be further granularized, and "old versions" supported much more easily.
It could also open up some form of "specify the matrix versions you want" via crate features, which then define/undefine specific endpoints/versions/features by macros.
More info: https://spec.matrix.org/v1.1/#endpoint-versioning
The text was updated successfully, but these errors were encountered: