Refactor usages of fetchConversation

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>

1 files changed, 5 insertions, 4 deletions

diff --git a/src/PublicShareAuthSidebar.vue b/src/PublicShareAuthSidebar.vue
index e30f9b70d..11dbfac2f 100644
--- a/src/PublicShareAuthSidebar.vue
+++ b/src/PublicShareAuthSidebar.vue
@@ -42,7 +42,6 @@ import CallView from './components/CallView/CallView'
 import ChatView from './components/ChatView'
 import { PARTICIPANT } from './constants'
 import { EventBus } from './services/EventBus'
-import { fetchConversation } from './services/conversationsService'
 import {
 	joinConversation,
 	leaveConversationSync,
@@ -165,15 +164,17 @@ export default {
 			}
 
 			try {
-				const response = await fetchConversation(this.token)
-				this.$store.dispatch('addConversation', response.data.ocs.data)
+				await this.$store.dispatch('fetchConversation', { token: this.token })
 
 				// Although the current participant is automatically added to
 				// the participants store it must be explicitly set in the
 				// actors store.
 				if (!this.$store.getters.getUserId()) {
+					// Set the current actor/participant for guests
+					const conversation = this.$store.getters.conversation(this.token)
+
 					// Setting a guest only uses "sessionId" and "participantType".
-					this.$store.dispatch('setCurrentParticipant', response.data.ocs.data)
+					this.$store.dispatch('setCurrentParticipant', conversation)
 				}
 			} catch (exception) {
 				window.clearInterval(this.fetchCurrentConversationIntervalId)