You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Android - Chat - Unread message does not disappear from LHN in focus mode #7903
Removed shouldFilterReportIfRead as we need to filter both read & unread reports and used hideReports in shouldFilterReport along with existing criterias.
This should be enough to handle this issue.
Thanks!
Hmm, @Santhosh-Sellavel could you please help me understand why this is a bug?
The unread report is the most recent report. It shouldn't disappear once we've read it.
It should disappear only if we've read it, anddd we navigate to a different report.
I think this isn't a bug and we shouldn't remove unread chats from LHN. If we only keep pinned chats in the LHN then how the user would know about the new messages from a chat that isn't pinned by the user, it's not a good ux
If we assume that NewDot is supposed to work the same on all platforms then, when the current chat is open in the main view, it'd also be shown in LHN, on web/desktop. I think, in the screen vid in the OP, that it's not disappearing because the user hasn't navigated to a new report
Activity
MelvinBot commentedon Feb 25, 2022
Triggered auto assignment to @marcaaron (
Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.MelvinBot commentedon Feb 25, 2022
Triggered auto assignment to @jboniface (
External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.Santhosh-Sellavel commentedon Feb 25, 2022
Proposal
In here, For sidebar Options in focus mode, we have a filter for read reports alone. Using
hideReadReports: trueApp/src/libs/OptionsListUtils.js
Lines 706 to 711 in 53a9891
hideReadReportsis configurable filter criteria for the getOption methodApp/src/libs/OptionsListUtils.js
Line 351 in 53a9891
In the following lines, report gets filtered only when it has
report.unreadActionCount === 0App/src/libs/OptionsListUtils.js
Lines 410 to 419 in 53a9891
Since
hideReadReportscriteria is used forsidebarOptionsalone, we remove the criteria.Add a new criteria
hideReportsingetOptionsmethod.Now use
hideReportsin the filter and refactor the filter block as shown below.Removed
shouldFilterReportIfReadas we need to filter both read & unread reports and usedhideReportsinshouldFilterReportalong with existing criterias.This should be enough to handle this issue.
Thanks!
MelvinBot commentedon Feb 28, 2022
@jboniface Whoops! This issue is 2 days overdue. Let's get this updated quick!
jboniface commentedon Feb 28, 2022
post here https://www.upwork.com/jobs/~0148dbc5ffaba75ff9
3 remaining items
MelvinBot commentedon Feb 28, 2022
Triggered auto assignment to Contributor-plus team member for initial proposal review - @rushatgabhane (
Exported)MelvinBot commentedon Feb 28, 2022
Triggered auto assignment to @marcaaron (
Exported), see https://stackoverflow.com/c/expensify/questions/7972 for more details.rushatgabhane commentedon Mar 3, 2022
Hmm, @Santhosh-Sellavel could you please help me understand why this is a bug?
The unread report is the most recent report. It shouldn't disappear once we've read it.
It should disappear only if we've read it, anddd we navigate to a different report.
I hope I'm making sense
Santhosh-Sellavel commentedon Mar 3, 2022
@rushatgabhane
My learnings here, on focus mode we can just have selected chats alone, and ignore other chats.
Also, Issue was reported by Applause here.
rushatgabhane commentedon Mar 3, 2022
Do you agree that this issue should be closed?
thesahindia commentedon Mar 3, 2022
I think this isn't a bug and we shouldn't remove unread chats from LHN. If we only keep pinned chats in the LHN then how the user would know about the new messages from a chat that isn't pinned by the user, it's not a good ux
Santhosh-Sellavel commentedon Mar 4, 2022
@rushatgabhane I am 50-50 here, so let's ask in the Slack channel to get an opinion on what's expected here.
Santhosh-Sellavel commentedon Mar 4, 2022
Asked in channel thread link
rushatgabhane commentedon Mar 5, 2022
Great, thanks. Added my thoughts in the 🧵
rushatgabhane commentedon Mar 14, 2022
@marcaaron we've reached a consensus to close this issue in this slack thread.
marcaaron commentedon Mar 14, 2022
Sounds good thanks