I think it is basically so that you can check validation, you can set items dirty, pristine, etc, or add error messages for each element- take a look here:
http://www.ng-newsletter.com/posts/validations.html notice where error messages are introduced, they are accessed off the form by its name On 3 September 2014 08:00, Eric Eslinger <[email protected]> wrote: > Help me become better in-formed. See what I did there? > > But seriously. I've been building a bunch of UIs using angular, and I > never seem to use ng-form or forms at all. I've got interface elements like > inputs and selects, and a button that runs the data submission, but the > data are stored in my $scope on models, and the ng-click validates the > models and does an XHR. > > I feel like I'm missing some kind of core functionality, or I've just > never needed it. OTOH, my DIY (and janky) front end ORM has its own form of > dirty-checking and validation anyway, so maybe I just never needed it. > > So my question: what's the use case for using actual <form> tags on the > page? > > e > > -- > You received this message because you are subscribed to the Google Groups > "AngularJS" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/angular. > For more options, visit https://groups.google.com/d/optout. > -- Tony Polinelli -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
