Feature Request: Dynamically add ng-message to ng-messages

[adrianandreias]

Add the ability to programaticaly add ngMessage item to an existing ngMessages directive.

I am trying to show the field error returned by an AJAX form submit. This way frontend errors and backend errors displaying would be done the same way.

Do you this is the right approach or you would just create another way to insert the server side error in the DOM?

[caitp]

I'm not sure why you'd need this, since we already have async validation, so you could just set up a message for the particular async error you're validating against. While we could allow you to add new messages, I feel like it would make the API cumbersome, so we'd have to think about this.

@petebacondarwin / @matsko thoughts?

[adrianandreias]

From my understanding if the error message itself comes from the backend async validation doesn't help.

Sounds pretty limiting to me to only define the list of error message in HTML.
There could be other scenarios where you want to define error messages at run time.

Not sure what this modification implies but shouldn't be hard to add add/remove/modify message functions.

[matsko]

@adrianandreias @caitp I think having dynamic messages is a great idea. The problem is that we can't use something like ng-repeat since there would be a conflict over how the elements are entered and removed from the ng-messages container, but if we can get that to work then it would open up a bunch of possibilities. I think it would be better if we keep as much of the message handling as possible in the HTML instead of having an imperative solution then we can do a lot more stuff.

It would be ideal if we could have something like:

<div ng-messages="myForm.myField.$error">
   <div ng-message="required">You did not enter a field</div>
   <div ng-message="key" ng-repeat="(key, message) in remoteMessages">
      {{ message }}
   </div>
</div>

@adrianandreias would this work for you?

[adrianandreias]

Sure, I assume we can have $scope.remoteMessages = [] in controller initialization and if on form submit there's an error message returned from the server you'd just push it in remoteMessages and then call $setValidity.

If this is the whole idea it's perfect.

(btw @matsko I love your site!)

[jessemorton]

I'd love to see this as well. There's plenty of cases where an async validator is impractical/overkill for all the fields in a form, but that it'd be desirable to display backend errors if they arise upon form submission.