test(watch): watching a reactive array #10848
Merged
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.
These tests were inspired by the changes in #9417. I don't think the changes proposed there can be merged as they would break backwards compatibility, but I found it interesting that they didn't cause the existing tests to fail.
It seems we have relatively few tests for
watch(reactiveArray, ...)
, and in particular how it differs fromwatch(plainArray, ...)
. I experimented locally and found I was able to introduce various bugs without triggering any test failures.Here I've aimed to test 3 ways that reactive arrays behave differently from plain arrays when passed as a source to
watch
:newValue
oroldValue
passed to the callback.deep: true
by default.deep: false
should be watched one level deep, starting from the array itself.