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 }}
This repository has been archived by the owner on Apr 25, 2023. It is now read-only.
Currently when a next message is added and route is changed, the new status becomes unseen.
Is there any design-driven reason for that? Could the state be changed to shown instead? We are showing the message in the new state anyway, aren't we?
My use-case is this. State A adds next message "ab" and triggers transition to state B. While at state B, some new messages are added with status shown. Now at some point (on user action) I want to clear all showed messages, including those coming from previous state (such as "abc"). But since "abc" is "unseen", removeShown() cannot be used for that.
I know I could call markShown() just before removeShown() for this case, but that looks more like a workaround to me.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently when a
next
message is added and route is changed, the new status becomesunseen
.Is there any design-driven reason for that? Could the state be changed to
shown
instead? We are showing the message in the new state anyway, aren't we?My use-case is this. State A adds
next
message "ab" and triggers transition to state B. While at state B, some new messages are added with statusshown
. Now at some point (on user action) I want to clear all showed messages, including those coming from previous state (such as "abc"). But since "abc" is"unseen"
,removeShown()
cannot be used for that.I know I could call
markShown()
just beforeremoveShown()
for this case, but that looks more like a workaround to me.The text was updated successfully, but these errors were encountered: