-
Notifications
You must be signed in to change notification settings - Fork 267
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
fix(stubs): teleport stub children as a function #1833
fix(stubs): teleport stub children as a function #1833
Conversation
✅ Deploy Preview for vue-test-utils-docs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have no better solution for this.
Can you add a spy on console.warn
on one of the teleport tests?
4bb8fd8
to
250610c
Compare
@freakzlike I added a test to check that the warning is not logged anymore, and added a check in other tests when it is logged, but when that we expect it. Maybe we should do the same for the warnings logged by vue compact (either mock them or fix them if needed) to avoid polluting the test logs, and missing a regression like this one in the future Anyway, this should fix the issue, unless someone comes up with a better idea. I'll let you give a last check and merge |
250610c
to
60268e6
Compare
This does feel like a bit of a hack, but okay for now. I am not sure of a better way. Warnings are not much fun. let's merge this up with one more ✅ and release. |
Fixes #1829
I'm not super convinced by this fix, but it indeed looks like @freakzlike intuition is right: we need to return the children as a function for Teleport to avoid the warning.
Maybe @xanf you have a better idea on how to handle that?