-
Notifications
You must be signed in to change notification settings - Fork 213
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 heroes
and room summary fields to Sliding Sync /sync
#17419
Merged
Merged
Changes from 15 commits
Commits
Show all changes
22 commits
Select commit
Hold shift + click to select a range
9deb387
Initial work of adding name/avatar to rooms response
MadLittleMods b0bb37f
Add tests
MadLittleMods b6e36ef
Add changelog
MadLittleMods 6ef39dd
Actually test that invited should see current state
MadLittleMods 32c5409
Start of heroes in Sliding Sync
MadLittleMods 9641ca7
Merge branch 'develop' into madlittlemods/sliding-sync-room-name-avatar
MadLittleMods 9692c76
Merge branch 'madlittlemods/sliding-sync-room-name-avatar' into madli…
MadLittleMods ee9114c
Merge branch 'develop' into madlittlemods/sliding-sync-heroes
MadLittleMods f58d6fc
`heroes` is not `required_state` for now
MadLittleMods 82bf80c
Add changelog
MadLittleMods 10f8540
Add tests
MadLittleMods 62925b6
Remove unncessary check
MadLittleMods b9f1eb1
Test `joined_count`/`invited_count`
MadLittleMods e50bf86
Test invite before/after ban
MadLittleMods 2fb77b3
Sort `leave` before `knock`
MadLittleMods 275da50
Explain the order
MadLittleMods 6060408
Add test to make sure we only return 5 heroes
MadLittleMods 91cefaa
Fix lint
MadLittleMods 868dcdc
Revert `heroes` order changes
MadLittleMods a4753bf
Better comment on what we expect
MadLittleMods 5583ac1
Merge branch 'develop' into madlittlemods/sliding-sync-heroes
MadLittleMods e2138b7
Have to use basic assertion for now
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 @@ | ||
Populate `heroes` and room summary fields (`joined_count`, `invited_count`) in experimental [MSC3575](https://github.com/matrix-org/matrix-spec-proposals/pull/3575) Sliding Sync `/sync` endpoint. |
Large diffs are not rendered by default.
Oops, something went wrong.
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -200,9 +200,6 @@ class SlidingSyncList(CommonRoomParameters): | |
} | ||
|
||
timeline_limit: The maximum number of timeline events to return per response. | ||
include_heroes: Return a stripped variant of membership events (containing | ||
`user_id` and optionally `avatar_url` and `displayname`) for the users used | ||
to calculate the room name. | ||
filters: Filters to apply to the list before sorting. | ||
""" | ||
|
||
|
@@ -270,7 +267,6 @@ class Filters(RequestBodyModel): | |
else: | ||
ranges: Optional[List[Tuple[conint(ge=0, strict=True), conint(ge=0, strict=True)]]] = None # type: ignore[valid-type] | ||
slow_get_all_rooms: Optional[StrictBool] = False | ||
include_heroes: Optional[StrictBool] = False | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Removed |
||
filters: Optional[Filters] = None | ||
|
||
class RoomSubscription(CommonRoomParameters): | ||
|
Oops, something went wrong.
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.
By changing this now, it will probably cause peoples rooms names to calculate to something different across the board (this function is also used by Sync v2). Are we ok with that? Potentially disruptive if people are really used to their old "flawed" name.
It's already a
FIXME
comment inextract_heroes_from_room_summary(...)
but we still need to pull in the right order from the database.Related to matrix-org/matrix-spec#1334
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.
Why do we need to change the order now? I think we only need to have a "stable" ordering?
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.
The spec says this:
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.
Hmm, interesting. Can we keep as is for now and open a separate PR / issue to consider this? I'm failing to think through whether this is going to cause some UX issues or not
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.
Reverted in this PR and split out to #17435 ⏩