-
Notifications
You must be signed in to change notification settings - Fork 228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add room_types
/not_room_types
filtering to Sliding Sync /sync
#17337
Merged
MadLittleMods
merged 9 commits into
develop
from
madlittlemods/msc3575-sliding-sync-filter-room-types
Jul 2, 2024
Merged
Changes from 3 commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
cf285ca
Start of filtering `room_type`
MadLittleMods fe77f4f
Filter by `room_types`/`not_room_types`
MadLittleMods f10b614
Add changelog
MadLittleMods 9a696d8
Merge branch 'develop' into madlittlemods/msc3575-sliding-sync-filter…
MadLittleMods fcf271a
Merge branch 'develop' into madlittlemods/msc3575-sliding-sync-filter…
MadLittleMods d8ad642
Merge branch 'develop' into madlittlemods/msc3575-sliding-sync-filter…
MadLittleMods 4473ec4
Update wording of fixme
MadLittleMods d6894d3
Merge branch 'develop' into madlittlemods/msc3575-sliding-sync-filter…
MadLittleMods 0a3261c
Merge branch 'develop' into madlittlemods/msc3575-sliding-sync-filter…
MadLittleMods File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
Add `room_types`/`not_room_types` filtering to experimental [MSC3575](https://github.com/matrix-org/matrix-spec-proposals/pull/3575) Sliding Sync `/sync` endpoint. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
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.
This doesn't affect this PR because we're just looking at the create event which we will always have but I'm curious about this for
get_state_at(...)
in general.For state in a room, do we have to worry about gaps? What happens if we try to get state a point in the room we haven't backfilled before?
I guess I just don't know if we have all historical state in the room. I know we have the whole auth chain of things which will be a subset of state 🤔
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.
@erikjohnston Is this a legit concern?
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.
Talked with @erikjohnston and got some knowledge.
In general, asking for state at a random position is dubious and we should careful about our usages.
It's not a problem in our current Sliding Sync usages because we're using it with the
to_token
which is at the front of the room so there will always be some latest event before theto_token
to get state at that positon.