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.

Warn about v-model components not handled with fireEvent.change

See original GitHub issue

More often than not people relies on fireEvent.input or fireEvent.change to handle v-model powered inputs, thus running into issues with input value not being properly updated.

I’m wondering if we should provide some kind of warning when that happens.

Does it make sense?

Issue Analytics

State:
Created 4 years ago
Reactions:3
Comments:16 (13 by maintainers)

Top GitHub Comments

2reactions

chiptuscommented, Nov 5, 2019

I actually found a very nice solution, I’ll try to post an example

0reactions

afontcucommented, Nov 20, 2020

Since this was released in #166, I’ll go ahead and close this issue, feel free to open up a new one if we’re missing some warnings!

thank you all!

Top Results From Across the Web

How to fire an event when v-model changes? - Stack Overflow

How to fire an event when v-model changes? · 3. fiddle link is no longer working. · If the intent of calling foo()...

Component Events | Vue.js

Emitting and Listening to Events #. A component can emit custom events directly in template expressions (e.g. in a v-on handler) using the...

Examples - Testing Library

Example using v-model : // Get the input DOM node by querying the associated label. // Updates the <input> value and triggers an...

React Testing Library and the “not wrapped in act” Errors

In test, the code to render and update React components need to be included in ... So in most cases, we do not...

Handling Events :: Eloquent JavaScript

Event listeners are called only when the event happens in the context of the object they are registered on. <button>Click me</button> <p>No handler...