This repository was archived by the owner on Apr 12, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 27.4k
ngMessageDefault - Add support for showing values not mapped with ng-message #12008
Milestone
Comments
gdangelo
added a commit
to gdangelo/angular.js
that referenced
this issue
Jun 25, 2015
Added support for showing default message when no values are mapped with ng-message. Closes angular#12008
gdangelo
added a commit
to gdangelo/angular.js
that referenced
this issue
Jul 5, 2015
Added a new param (boolean, isDefault) to the factory ngMessageDirectiveFactory, in order to reuse code in ngMessageDefault directive. Closes angular#12008
Sorry to push it, but could someone tell me what is the status? Will it not be included in the release? |
This will go into 1.6 as soon as 1.5.0 is out; since we have locked down 1.5 features now in preparation for a release very soon. |
+1 |
Marked with "PRs plz" which indicates we would accept a community contribution for this issue. |
I'm planning to work on this. I'll probably start with the code from #12213 and make changes requested in the comments. |
@4O4 That's great to hear! |
Narretz
pushed a commit
to Narretz/angular.js
that referenced
this issue
Jun 1, 2018
Added support for showing default message when no values are mapped with ng-message. Closes angular#12008
3 tasks
Narretz
pushed a commit
to Narretz/angular.js
that referenced
this issue
Jun 1, 2018
Added support for showing default message when no values are mapped with ng-message. Closes angular#12008
Narretz
pushed a commit
to Narretz/angular.js
that referenced
this issue
Jun 1, 2018
Added support for showing default message when no values are mapped with ng-message. Closes angular#12008
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Many times it is necessary that we show a generic error message for unexpected values.
Would be nice to have something like:
This way, whenever there is an "error3" in "controller.errors", as it is not mapped, the value under the ng-message-default would be shown.
The text was updated successfully, but these errors were encountered: