Fix: nested-with-vmodel example not really trigger vuex actions #1210
+12
−9
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gong9
changed the title
gong9
changed the title
hexiaokang
approved these changes
Jun 8, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Regarding the example of nested-with-vmodel, I have noticed that using computed sometimes does not trigger the modification of data in Vuex. Even if it appears that the data has changed on the page, it does not seem to be caused by Vuex behavior. This may be due to my limited knowledge of Vue, but I believe it is the data reference behavior of computed itself.
It is important to note that only when the first layer of data in the nested-test component changes will it trigger the set of elements.