-
-
Notifications
You must be signed in to change notification settings - Fork 247
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 button to view @ mentions. #433
Conversation
One thing I noticed is that if there are two message of the same narrow (say #zt>some topic), and if I narrow using one of them via |
@amanagr Not sure why, But I'm not able to reproduce this. How are you coming back to the My steps:
Am I doing anything wrong? |
I am also unable to reproduce it now :| |
860611d
to
4ceebf5
Compare
4ceebf5
to
b732385
Compare
@neiljp FYI. Updated this with tests. Its now ready for a review. |
b732385
to
2c51ab0
Compare
@neiljp Resolved conflicts and rebased this. Do you have time to give it a review? |
2c51ab0
to
32cc6e0
Compare
785f430
to
f6e5301
Compare
This PR has be split up as :
I have separated the commits which involve the scenario when a mentioned message is received after ZT has started. I have kept these in a separate branch and will work on these shortly. |
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.
@sumanthvrao Thanks for looking at this again - it may just be 3 fewer commits, or the reworking you did, but this feels good 🎉
I think if the first 6 commits (by git, not per github!) can be polished then these will allow a good initial partial merge, allowing the narrowing to work with #
(maybe with that squash mentioned). Then the button code and dynamic updates can be integrated separately.
Hopefully the comments are clear, but as always let me know here and/or on czo.
f6e5301
to
618b3fb
Compare
@neiljp Thanks for the review. I have updated the PR with the changes requested. |
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.
@sumanthvrao Other than the possible extra comment note and Narrow to
in the README/help_text, I'd like to merge the first 5 commits ASAP. You have a different git name for one of those commits though - if you want to maintain the original name, we can do that before merging those 5 too.
I've left a small note re the button spacing; there may be a few other issues, but I've run out of time to look further right now.
The new commit message was because I squashed 2 commits from the previous version. I have updated the commit heading to be the first one of the squashed commits.
Besides this, if there are no more changes, let's get it merged ASAP :) |
5a52631
to
993cf2a
Compare
@sumanthvrao The first 5 are merged; now onto more UI :) 🎉 I think the other work is updating while ZT is running, and possibly the all-mentions aspect? |
Thanks @neiljp ! |
993cf2a
to
eb0a253
Compare
If user is in 'mentioned' view and a new mentioned message arrives, we need to append it to current view. Tests added.
On startup, we classify any unreads which belong to mentioned stream so that we can mark the MentionedButton with the correct mentioned count. Tests added.
eb0a253
to
d839729
Compare
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.
LGTM!
I've tested this locally and everything works great for me.
Also, the commits look concise and well organized. 👍
Thanks for the review @kaustubh-nair! Glad to see there are no errors. :) |
@sumanthvrao I just merged the rest of these commits manually, after slightly adjusting the last one to fit with the recent changes to Some commits are quite small, but we put in a lot of related effort before this - though some extra tests may be warranted? |
@sumanthvrao Awesome work! This looks great. 👍 |
@neiljp Thanks for taking time to review this and I'm glag to finally get it merged. Thanks @preetmishra :) |
This PR adds support to view
@
mentioned messages. Any feedback regarding this is welcomed.Solves #425