Here is the general situation: you have a form, and you are interested in the representations of this form. You can add wrinkle to the situation by adding a server validator or even a client-side validator, but validators are provided only as a means of providing the input you send, in this case; any state collected between 0 and sending is also thrown randomly.
There is a less common situation here: in your form there is a password / confirmation field that needs to be laid out in order to work with the obvious manner and wire in order to display an indication of the strength of the password (and validity). I used to see a lot of "write jQuery callbacks for the event handler on change and call it day." This is just an extreme case when it is necessary for the state between them to reach their destination, and not as an end in itself.
Now a very unusual situation: you need to track the contribution of this form, because it is a form used by the US government to communicate with our guys in nuclear bunkers in Wyoming. Of course, it is important that the form input is valid when submitting, but we need to additionally know how much we can about how it got there. Let's say this is a login form, for example. If we track the sequence of events from 0 to the view and compare it with the past, we can detect anomalies in user behavior, for example. We can determine if we have problems with the servers before we find out about them. Therefore, this is not always emission information.
I want to match the event onChangewith the concept of Diode, but it's hard for me to understand what I should do. Here are the options:
case class ( ).- , " ", . , , , , , .
- ,
Pot s, Scratch. , , , .
, ... .