Greg Slepak
Greg Slepak
> Where is version v1.07 ? I can only find v1.06 Oops, I meant 1.0.6!
Based on this call: - Increase KV notification status memory to 2 months - Increase Vuex notification memory to 6 months - Automatically mark notifications as read after the notification...
Closed by @corrideat in #2333.
Edited issue to add: > EDIT: similar changes may need the done for `/get`, please [see this message on Slack](https://okturtles.slack.com/archives/C0EH7P20Y/p1722966450525149) about an error.
> I think a better solution is to leave the API as is, and instead write a wrapper for this common use case. That would address the DRY concern, keep...
> They may look ugly, but I think they're necessary. Besides keeping things in sync, they also help debug issues, as the relevant call is logged this way. I'm not...
> They're (they = the queued invocations, not the specific decision to use selectors) necessary because they put a barrier that forces the order of login and logout events. These...
OK, maybe this issue has been fixed mysteriously, but there is another set of heisenbugs in `group-chat.spec.js` that are documented here: #2256 .... EDIT: oh i see, maybe #2294 fixes...
Might've been fixed by @corrideat in #2294
@SebinSong yep, those in-app notifications.