chore: test failure with vue v3.1.0-beta.2 #3294
Closed
Conversation
This file contains 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
logaretm
added a commit
that referenced
this pull request
May 8, 2021
|
Thanks for the heads up, after some investigation this is caused by this change in Vue core. I have found a workaround for this that seems backward compatible, will tag a release shortly to mitigate this coming up. |
|
|
|
It works with 4.3.6, awesome 👍 Thanks @logaretm |
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.
🔎 Overview
👋 @logaretm
Just for the heads up: Vue v3.1.0-beta.2 is out, and our projects have test failures with VeeValidate when we bump to the new beta.
It looks like the same failures are occurring in your unit tests.
I don't know if it is a regression in vue-next or something that needs fixing with vee-validate...