| Age | Commit message (Collapse) | Author |
|---|
|
Signed-off-by: marco <marcoambrosini@pm.me>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: marco <marcoambrosini@pm.me>
|
|
The devices mixin logic is initialized when loading the app but the
devices shouldn't be initialised until the DeviceChecker's modal has
been opened.
Signed-off-by: marco <marcoambrosini@pm.me>
|
|
Signed-off-by: marco <marcoambrosini@pm.me>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
The audio encoder is initialized when the AudioRecorder component is
mounted, and the store keeps track of whether the audio encoder was
already initialized to not do it again.
However, the audio encoder was also unconditionally registered in the
main components of the main and sidebar Talk UIs, which caused a
duplicated registration when the audio encoder was initialized (as the
store did not "know" that it was already registered).
Due to all this the unconditional registration is removed (which also
avoids registering the audio encoder when it will not be needed, like
when the current user is a guest without upload permissions).
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
audiorecorder component
Signed-off-by: Marco Ambrosini <marcoambrosini@pm.me>
|
|
Moved joinConversation, leaveConversation and a few other dependencies
to the participantsStore.
Removes the dependency to the store from participantsService.
There's a slight change of behavior: joinConversation in the service now
also connects to signaling, and only when this is done the first
action dispatch are done. In the previous implementation the store
already received some updates before we even connected to signaling.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Instead of calling the service's "fetchConversation" method and manually
adding to the store, use the new "fetchConversation" store action that
does that directly
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
When joining a conversation, don't mark it as read any more.
The only moment will be when scrolling down to the bottom of a
conversation and when clearing the read marker, in which case we
immediately update the store.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Fix redirect when deleting current conversation
|
|
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
When the current conversation was deleted while in a call, or
whenever someone has been removed from a room, the redirect
now targets the not-found page instead of the one about duplicate
session.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Merge deleteConversation that takes a conversation object with
deleteConversationByToken since only the token is needed anyway.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
To remove duplication of the "get current participant" logic all over
the place and also for future use.
Signed-off-by: Vincent Petry <pvince81@yahoo.fr>
|
|
Fixes chat in sidebar for video verification and when chatting about a
file from a public link.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Otherwise there is no update of the computed and the call screen will not show up.
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
The room participants update events are sent by the external signaling
server:
-When a user resumes the session
-When an internal client joins or leaves the conversation
-When the BackendNotifier sends a "participants" event (that is, when
the type of a participant changes, when the name of a guest changes or
when guests are cleaned)
-When the BackendNotifier sends a "incall" event (that is, when a
participant joins or leaves the call)
In all those cases it is not really needed to fetch all the
conversations to get the updated state, but only the current
conversation. Note that it is not enough to fetch just the participants,
as for example when a call is started that modifies some attributes in
the conversation, like "hasCall".
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
Signed-off-by: Marco Ambrosini <marcoambrosini@pm.me>
|
|
Signed-off-by: Marco Ambrosini <marcoambrosini@pm.me>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Marco Ambrosini <marcoambrosini@pm.me>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
The button is disabled and a loading icon is shown next to its text.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
