Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
DOMWrapper: setValue
See original GitHub issuecombines setSelected, setChecked` etc as per https://github.com/vuejs/vue-test-utils-next/issues/17#issuecomment-604367645
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (10 by maintainers)
Top Results From Across the Web
DOMWrapper: setValue · Issue #29 · vuejs/test-utils - GitHub
Rename current setChecked to setValue , and make sure current tests keep passing (after updating the public API, of course). copy&paste ...
Read more >setValue - Vue Test Utils
setValue. Sets value of a text-control input or select element and updates v-model bound data. Arguments:.
Read more >wrapper.setValue() cannot be called on EL-INPUT
wrapper.find() returns a DOMWrapper . The setValue() implementation on the DOMWrapper only allows you to use it on input , textarea ...
Read more >DomStringWrapper (Unofficial IntelliJ Community Edition API docs)
public class DomStringWrapper extends DomWrapper<java.lang.String> ... setValue. public void setValue(java.lang.String value) throws java.lang.
Read more >Testing issues: setValue() cannot be called on ION-INPUT
Actual test error: Cannot call setValue on an empty DOMWrapper. Has anyone had any success with testing a Vue component that is using...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The way I was expecting this to go is we keep
setCheckedetc, but make themprivate. ThensetValuejust checks the type of the element, and calls the correct one. But any implementation is fine. I think we should copy paste the tests for setChecked, setSelected etc where we can from beta.Yes! I will have to go in exactly 1h 😃