Skip to content

New socket instance created if vuex’s store mutation function called inside socket #338

@JH-Eric-Yang

Description

@JH-Eric-Yang

Hi, I tired to call a mutation function in the vuex's store inside a socket event listener. It looks something like this

import { createStore } from "vuex";

export default createStore({
    state() {
        return {
            message: "default message",
        };
    },
    mutations: {
        SOCKET_updateMessage(state, message) {
            console.log("SOCKET_updateMessage: message:", message);
            state.message = message;
            this.updateMessage(message);
        },
       
	 updateMessage(message) {
            console.log(message)
	        },
    },
});

It will work but I notice that it will recreate a new socket instance. The client will create and communicate with the server with the new socket instance (with different socket.id). I wonder why this is happening. Thank you.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions