filter is still saving the mutation to localforge

Currently I have:

const ignoreMutations = [
  'currentUser/setAuthenticated',
  'currentUser/setLoggedIn',
  'resource/setTypes',
  'resource/setCurrentVideo',
]

const vuexPersist = new VuexPersist({
  asyncStorage: true,
  key: 'vuex',
  storage: localForage,
  filter: mutation => !ignoreMutations.includes(mutation.type),
}).plugin

When I check localforge the data has been saved, shouldn’t this not be the case?

[cj]

@championswimmer I see why it’s not working as I expected. https://github.com/championswimmer/vuex-persist/blob/master/src/index.ts#L169-L172 It’s saving the entire state regardless of what the mutation is. So lets say you have a state like:

export const state = () => ({
  authenticated: false,
  loggedIn: false,
  data: {},
})

and you have 3 mutations setAuthenticated, setLoggedIn and, setData; If I have the following config that I showed above:

const ignoreMutations = [
  'currentUser/setAuthenticated',
  'currentUser/setLoggedIn',
  'resource/setTypes',
  'resource/setCurrentVideo',
]

const vuexPersist = new VuexPersist({
  asyncStorage: true,
  key: 'vuex',
  storage: localForage,
  filter: mutation => !ignoreMutations.includes(mutation.type),
}).plugin

If the mutation setData gets called, it is still going to save the state for authenticated and loggedIn, as it’s saving the entire state. I think what it should do instead is just deep merge in the mutation data.

[my3188]

@cj How did you finally solve this problem