follow-up(messageStore): fix hasCall reactivity

Open
#10,648 0 comments 0 reactions 1 assignee View on GitHub

@Antreesy is already working on this.

Since Oct 6, 2023.

Assessment

This issue has not been assessed yet.

Description

bug feature: call 📹 feature: conversations 👥
How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

It takes a significant amount of time to trigger conversation update, although system messages started the call and ended the call are already received => causes issue for functions, which are dependant on conversation.hasCall state

Steps to reproduce

  1. Start call
  2. End call
  3. See LeftSidebar
Expected behaviour

Conversation is updated together with system messages

Actual behaviour

Conversation is fetched separately, with delay up to 30 seconds

Talk app

Talk app version: 17+

Custom Signaling server configured: yes

Dominant language
PHP
Stars
2.2k
Forks
587
Avg merge
17h 55m
Merged PRs (30d)
350

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nextcloud/spreed

All issues in nextcloud/spreed

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.