Yeah, ngMessage/ngMessages look like a promising addition compared to what folks have had to do so far. Even with ngMessages though, there's still a lot of duplication in the view (HTML) for validations that could/should be model/service based. I *think* formFor will still be attractive, even once 1.3 and ngMessage is out of beta.
On Monday, August 11, 2014 11:15:27 PM UTC-7, Sander Elias wrote: > > Hi Brian, > > Did you see the upcoming ng-messages > <https://docs.angularjs.org/api/ngMessages> from Matias Niemelä? I think > it needs some more work, but it's a good start. > For myself I prefer to put in the error messages inside the template, but > I would like to see less boilerplate as > is needed now, or even with the solution of Matias. > > Regards > Sander > -- 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.
