This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Move MSC3030
/timestamp_to_event
endpoint to stable v1 location #14471Move MSC3030
/timestamp_to_event
endpoint to stable v1 location #14471Changes from all commits
0312ad3
80a2b96
ee00b8d
d73088f
ed1180a
e702a5d
394d917
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we file an issue for this and add it to the Revisit: Next Year milestone?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FWIW in the past I've just never removed the failover logic for new endpoints.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
-> #14577
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just matched what
/threads
was doing sinceclient_patterns(...)
seems to be doing weird stuff withapi/v1
andunstable
by default. Not sure why those are things for normal endpoints.synapse/synapse/rest/client/relations.py
Line 85 in a84744f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we're trying to not use
client_patterns()
anymore since it hides a lot of logic.Is anything using the unstable version that we need to care about or can we just swap right away?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I only know of the Element Web jump to date UI and the Matrix Public Archive.
But those things are experimental along with this endpoint and have no guarantees. For jump to date as it is in Element, it just won't show up since the server will show no support for
org.matrix.msc3030
(I'm not worried if there is a period where that functionality disappears).matrix-js-sdk
to try to pull from both the old unstable and new place -> Prefer stable/timestamp_to_event
endpoint first - MSC3030 matrix-js-sdk#2915There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If those are checking for the version flag than it sounds like it should be fine! 🎉