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
DOMWrapper: setValue #29
Comments
Should we use this issue to track the removal of set methods from Vue Wrapper and the combination of |
Yep, I think that makes sense. This should be a fun ticket. We could copy paste the tests from beta (that's what I did for |
I'd like to work on this! Even though I might need some guidance 😇So, in short, I should:
After that (could be another PR, and could be done after alpha-0), it should be extended to handle VueWrapper elements. Am I in the right track? |
oh dang I am on it atm... Want me to push and you continue or just drop mine? |
oh no worries, keep on working on it :) will be busy for the next hour or so. I guess at some point we can split work and submit separate PRs 🤗 |
Yes! I will have to go in exactly 1h :) |
The way I was expecting this to go is we keep |
I was going to do that, but then I just left it as is, so you guys can comment on it. There were quite extensive tests on those methods, not sure if I should put them in the setValue spec or not. |
Just the ones you think are relevant! |
This does not seem to be documented on the Migrating page https://next.vue-test-utils.vuejs.org/migration/ |
This should have been backported to VTU v1 and include deprecation messages. Is that not the case? |
combines
setSelected
, setChecked` etc as per #17 (comment)The text was updated successfully, but these errors were encountered: