Added additional check before adding the ._error property #1657
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.
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
dev
branch.fix #xxx[,#xxx]
, where "xxx" is the issue number)Other information:
Sometimes an error may occur in nextTick. In this case an error message will be displayed in the console:
In Vue in the nextTick handler, the context is an optional parameter (https://github.com/vuejs/vue/blob/dev/src/core/util/next-tick.js#L87-L95):
In the
handleError
handler, the presence ofvm
is checked first, but later, if not, it is still called (https://github.com/vuejs/vue/blob/dev/src/core/util/error.js#L9-L30):Finally, vue-test-utils register global error handler and try to add the new
._error
property to thevm
parameter which can be undefined (https://github.com/vuejs/vue-test-utils/blob/dev/packages/test-utils/src/error.js#L4-L10):This PR adds extra checking in case.