Use Payload class with any type of data mutation #140
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR attempt to solve the special case raised in #138.
With the use of
Payload
class in any cases of data / path processed troughvuex-pathify
, it become trivial to know (when we make astore.subscribe
) if a mutation has been created by pathify.To sum up:
A deserialization can occur when we sync the store across tabs (with
vuex-shared-mutations
for example).Fix #138