-
Notifications
You must be signed in to change notification settings - Fork 668
fix(validators): support components returning render function from setup (fix #1596) #1600
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Any chance to add a test for this? |
@lmiller1990 I was expecting this 😅 I didn't add tests because I didn't find any existing tests related to this method nor validators in general in the code base. I’m not sure where these should be added, could you guide me a bit? |
Sure thing, just stick in here: https://github.com/vuejs/vue-test-utils/blob/dev/test/specs/mount.spec.js. This codebase avoids testing implementation details (good thing) and just tests things however the user would be do it (usually with There is already a test using the composition API plugin, you could copy and paste that one. Just make a component with a We are in the process of moving to Jest, but until then you need to build bundle each time you change anything in |
@lmiller1990 Thanks for the guidance, hope that fulfill your expectations, otherwise let me know! |
@LeBenLeBen if you have some time can you try merging the latest dev to your branch? We moved to jest, it should make it easier to fix the CI and get this merged. Sorry I didn't get back to you - I thought I had pinged you, I guess not. Can you merge in dev and push again? Everything should be green then and we can merge. |
@lmiller1990 Done! |
I’m not sure why it doesn’t work with Vue 2.5… I tried to update It seems that the oldest version supported is Vue 2.5.22. Does the compat test use the latest 2.5 patch or 2.5.0 ? |
If you are having trouble with an older failing just add a conditional to skip it, see here for an example: vue-test-utils/test/specs/mount.spec.js Line 98 in ba84544
Pretty keen to get this merged. |
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
The PR fulfills these requirements:
dev
branch.fix #xxx[,#xxx]
, where "xxx" is the issue number)