-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Room list v2 feature implementation (outdated checklist) #13635
Labels
Comments
Extremely early and unapproved designs show we might be interested in having an option to order favourites like regular rooms, so matrix-org/matrix-spec-proposals#2579 exists (it was about time anyways). This would include #4484 |
turt2live
added a commit
to matrix-org/matrix-react-sdk
that referenced
this issue
Jun 1, 2020
For element-hq/element-web#13635 This is an incomplete implementation and is mostly dumped in this state for review purposes. The remainder of the features/bugs are expected to be in more bite-sized chunks. This exposes the RoomListStore on the window for easy access to things like the new filter functions (used in debugging). This also adds initial handling of "new rooms" to the client, though the support is poor. Known bugs: * [ ] Regenerates the entire room list when a new room is seen. * [ ] Doesn't handle 2+ filters at the same time very well (see gif. will need a priority/ordering of some sort). * [ ] Doesn't handle room order changes within a tag yet, despite the docs implying it does.
This was referenced Jun 1, 2020
Merged
turt2live
added a commit
to matrix-org/matrix-react-sdk
that referenced
this issue
Jun 6, 2020
Originally this was intended to be done only in the importance algorithm, however it is clear that all algorithms will need to deal with this. As such, it has been put into the base class to deal with as we may override it in the future. This commit should be self-documenting enough to describe what is going on, though the major highlight is that the handling of the sticky room is done by lying to the underlying algorithm. This has not been optimized for performance yet. For element-hq/element-web#13635
turt2live
added a commit
to matrix-org/matrix-react-sdk
that referenced
this issue
Jun 6, 2020
For element-hq/element-web#13635 This adds support for: * Tag changes * DM changes * Marking our own rooms as read * Our own membership changes The remaining branch we didn't need was the alternate 'new room' branch, so it was removed. This is not optimized - optimization is deferred.
This was referenced Jun 6, 2020
This was referenced Jul 10, 2020
Convert ImportanceAlgorithm over to using NotificationColor instead
matrix-org/matrix-react-sdk#4949
Merged
This was referenced Jul 13, 2020
This was referenced Jul 13, 2020
jryans
added a commit
to matrix-org/matrix-react-sdk
that referenced
this issue
Jul 13, 2020
If a sublist changes from sticky top to sticky bottom in a single run of the logic (without passing through the default state), we were leaving the previous top position set. This handles them independently to resolve this. Fixes element-hq/element-web#14390 Maybe helps with element-hq/element-web#14443 For element-hq/element-web#13635
This was referenced Jul 13, 2020
Finally closing this and it's 2mb screenshots' worth of referenced PRs. Everything else is tracked in the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The core algorithm being used is tracked as #11743 - this issue is all about the UI/UX features which need implementing. It's a bit long.
This doesn't account for a huge number of features. See the project board for more information on what is when.
aria-label
s andaria-level
sAlgorithmic behaviour:
Tests (end-to-end as well as unit/integration tests):
The text was updated successfully, but these errors were encountered: