Add update method for model updates

[dfcook]

Add update method to handle form updates without having to call updateState

[dfcook]

references #22

[afontcu]

Looks good!

This made me wonder about the use cases for fireEvent.input or fireEvent.change - now that fireEvent.update handles everything (am I right?).

Should then fireEvent.update be the default way to go when interacting with inputs? It's great that it handles v-model, but I'm a bit torn that the API differs a bit from the standard events (input, change).

[afontcu]

quick question! Should this line return, instead of await? If not, why does it need to be different?

[dfcook]

I missed that, updated now.

WRT change and input, I hadn't considered that update may replace them all. I would rather expose them and allow the user the choice of which to use than deprecate them. What do you think?

[afontcu]

This actually leads me to another question...

I feel that just writing .input or .change, like the native events, makes a lot of sense. And it would be quite weird if fireEvent.input only worked in certain cases (when v-model is not used).

So... what if input and change would handle v-model properly, instead of creating a new event? Would it be hard?

[dfcook]

We could mask input or change, however we're still moving away from what is the idiomatic usage and taking away options from the end user (to use input or change as they are natively).

I'm not sure if there is an ideal solution here tbh, although I think update as it is here is probably the most flexible solution.

[afontcu]

You are right. Also adding a method is a non breaking change, while modifying the implementation of .input and .change might be. Let's add the update method and see how it goes!

[afontcu]

Looks great!