For many form, there are two streams available. To access the form, we need to use view child, look up that form ref through that reference, and then we'll just assign that to form. This is looking up this guy and bringing it down so we can control it programmatically.
We can access that in NG after view init because at this point in this lifestyle hook, the view is ready to go. We can say this.form, and then the form has a stream called value changes. We can subscribe to that and just log out or we'll table out just to give it nicely formatted the results.
I'll bring up the Chrome dev tools. You can see that it's logging out as I change these. I'll type password. You can see we have our object with a log in of username John and password pass right now. Every time this form changes, it's going to pass these value changes along.
There's also a stream called status changes. I'll just log this one out. This will actually log out every time the status of my form changes. Now it's invalid. It's back to valid, invalid, valid. You can check against these valid and invalid values.
With a decent understanding of RxJS, you can build out some pretty complex streams. We'll just do a simple example where I say import RxJS, add observable, and I'll need combine latest. I'm going to need observable itself, so I'll say observable from RxJS observable. I'm also going to want filter, so I'll grab the operator filter.
With these two operators and observable, I can build up something like we'll say observable, combine latest, and we'll want to combine this.form.statuschanges and this.form.valuechanges. We'll combine these, so I'll have a status and a value and combine these into an object of status and value.
On this I can filter. This will pass that object of status and value. But I'm only going to want the status on there. If status is valid, then I want to print out the value of that object. I'll console table value.
If I save and bring up the dev tools, I'll clear this out, you can see I'll only get changes when I'm making changes and the field is still valid.
I got JO but once I went less than JO, you'll see I'm making changes in the field that's invalid but I'm not getting them because I'll only get changes pushed through when the field is value. For this example, you could add this to local storage every time someone put in a valid change to the form and save it and ignore any changes to the form that were invalid.
They could always revert back to a valid state of the form.