-
Notifications
You must be signed in to change notification settings - Fork 378
missing data in some modules #388
Comments
Out of interest, how did you update your state inside modules? I ran into an issue, where Vue wouldn't properly update the state if the code looked like this: const state = () => ({
})
const mutations = {
UPDATE_AUTH(state, passed) {
state.token = passed.token
state.expire = passed.time
}
} instead of this: const state = () => ({
user: {}
})
const mutations = {
UPDATE_AUTH(state, passed) {
state.user.token = passed.token
state.user.expire = passed.time
}
} I think if Vue doesn't know what's going to change to being with in |
The export function state(): FamilyState {
return {
me: null,
};
}
export const mutations: MutationTree<FamilyState> = {
[SET_ME]: (state: FamilyState, me: Family) => (state.me = me),
}; However, within this other module the export const state = (): AuthState => {
return {
user: null,
token: '',
};
}
export const mutations: MutationTree<AuthState> = {
UPDATE_USER: (state: AuthState, user: User): User => (state.user = user),
UPDATE_TOKEN: (state: AuthState, token: string): string => (state.token = token),
}; I don't see any meaningful differences between these two modules. |
Considering that you're still on Vue 2, have you tried using the Vue Devtools and seeing if it picks up the mutation change? I don't TypeScript that well, but they look a bit different when it looks like you may be missing something (once again I don't know much about TypeScript), but it could be [SET_ME]: (state: FamilyState, me: Family)/*: Family */ => (state.me = me) that's' different. Also, it could just be completely irrelevant idk I'm not the brightest with TypeScript |
The mutation is recorded in the DevTools. |
vuex-persistedstate
version: 3.2.0node
version: 10.21.0yarn
version: 1.22.5nuxt
version: 2.14.12Relevant code or config
What you did:
I hopefully correctly followed the provided guides to config client/server synchronization of the Vuex store.
Problem description:
Not all of my modules are populated with information beyond the initial state. All state changes are completed using proper mutations.
Suggested solution:
Good question
The text was updated successfully, but these errors were encountered: