Because AngularJS general error messages still suck. ngMessages can kiss my ass.
TL;DR http://pocesar.github.io/angular-errorlookup
Made for Angular 1.4+, made in sexy Typescript
$ bower install angular-errorlookupHas jQuery and lodash as dependencies
How is it better than ngMessage / ngMessages? Or plain old ng-switch-when / ng-if directive and a bunch of divs?
Because you need to write the same boring HTML markup over and over, and you need to cluttering your scope and
controllers with useless state error messages. Plus, you are usually stuck with modelController.$error /
myForm.myModel.$error.required / myForm.$error.required[0].$error (srsly wtf) boolean states.
It's nearly impossible to $setValidity without a helper directive that has access to some sort of global state,
since the ngModel controllers and form controllers are only available inside directives that require them or tied
to a controller / scope. It's even worse, when you have to return validation from the server after a socket/ajax
call and show it in your form / models, or after async validation.
So, are you tired of no way of assigning errors dynamically, bypassing them when necessary? Does your scope variables look like a mess with state errors? How about show a simple plain string on a form or console without assigning it to a scope/controller variable?
Take this superb code for example:
<form name="userForm">
<div class="field">
<label for="emailAddress">Enter your email address:</label>
<input type="email"
name="emailAddress"
ng-model="data.email"
ng-minlength="5"
ng-maxlength="30"
required />
<div ng-messages="userForm.emailAddress.$error">
<div ng-message="required">You left the field blank...</div>
<div ng-message="minlength">Your field is too short</div>
<div ng-message="maxlength">Your field is too long</div>
<div ng-message="email">Your field has an invalid email address</div>
</div>
</div>
</form>Now multiply that for 20 fields! Awesome right?
This doesn't tie you with a controller or directives, and it doesn't aim to provide you a validation interface. (Use angular-async-validator for that)
This module aims to provide a D.R.Y. service for your errors, watching your models for ERRORS only
It's an application-wide error messages service with helper directives for the heavy lifting! ngMessages doesn't offer you a way to programatically set errors (unless you create a directive that requires ngModel and ngMessages, and you do the bridge, aka, hot mess).
You can use ErrorLookup in your DOM in a declarative manner, in your controller(s), in your directive(s), in services (biggest win!), it keeps all your error messages under complete control (along with access to the bound element, scope and attributes), and you can have them using translations as well.
Best of all: interpolation and callbacks! Make your errors beautiful and meaningful with magic. No more
useless boring generic messages like "Please fill this field" for every 350 fields in your forms and
copy pasting divs all over the place or making a damn directive that adds them after each of your
inputs, and the need to use $compile, and all of the haX, like appending divs to DOM without you
wanting it to.
The ErrorLookup provider and service is that holds all messages and instances, models and attributes from your elements so it can be the ultimate overlord of your errors (and messages, but mostly errors, since it checks the $error member of the ngModelController and FormController).
angular
.module('YourApp', ['ngErrorLookup'])
.config(['ErrorLookupProvider', function(ErrorLookupProvider){
// ErrorLookupProvider allows you to remove/add/overwrite your messages before your controllers load
ErrorLookupProvider.add('creditcard', 'The provided credit card isn\'t valid');
ErrorLookupProvider.add('cvv', 'The CVV {{ model.$viewValue }} isn\'t valid for {{ scope.cardType }}');
ErrorLookupProvider.add('repeated', 'The value {{ value }} doesn\'t match {{ models.fucker.model.$viewValue }}');
}])
.controller('MainCtrl',
['$scope', 'ErrorLookup',
function($scope, ErrorLookup){
// ErrorLookup is the full blown service
ErrorLookup.messages.types.email({value: 'name'}); // name is not a valid email
// Everything in types are a function from "$interpolate"
// You can overwrite them by using:
ErrorLookup.messages.add('email', 'O email "{{value}}" não é válido');
ErrorLookup.messages.types.email({value: 'name'}); // O email "name" não é válido
}
]);Easily retrieve localized messages from the server:
angular
.module('YourApp', ['ngErrorLookup'])
// just use the helper FFS
// assuming your json structure is:
/*
{
"required": "Você precisa preencher este campo",
"email": "O email \"{{ value }}\" é inválido",
"blacklist": "O <strong>email</strong> não é permitido"
}
*/
.run(['ErrorLookup', function(ErrorLookup){
// Load ALL the messages
ErrorLookup.messages.include('/error-messages.json').then(function(messages){
// changing messages change them internally before applying it
delete messages['required'];
});
}]);But that's only for adding and manually setting error messages, which isn't much different from adding stuff to your controllers. We want moar.
There are a couple of locals you can use in your string messages:
Pretty name of the model, instead of displaying "login.data.user.email" to the user, display
something like "Your email". On the directive, it's the value of error-lookup-label
The ngModel itself with all the bells and whistles, unchanged. On the directive, it's the
value of ng-model
This will only be available if it's triggered using error-lookup-form.
The $name is the assigned name using error-lookup-name, name or ng-model attributes.
The $attrs from the current element with all the bells and whistles, unchanged You can even add CSS classes to the element through here, omg messy spaghetti!
Alias for the current model $viewValue. If you want the $modelValue use $model.$modelValue.
The assigned scope. You may access your controller doing $scope.yourcontroller in here as well.
ALL the models in the current group! Means you can reference other ngModels, how cool is that?
Since it uses interpolation, you always need to run the curryed function returned
from the ErrorLookup.error(), since it has no watches and doesn't use $compile (that
watch over expressions automatically):
angular
.module('YourApp', ['ngErrorLookup'])
.controller('MainCtrl',
['$scope', 'ErrorLookup',
function($scope, ErrorLookup) {
$scope.error = ErrorLookup.error('MainCtrl', 'user.email');
// this function changes the internal error array of the current model everytime it's called, plus it returns
// the current error collection! (that is, an array of objects) So it's a setter AND a getter
// <div ng-repeat="error in error() track by error.message"></div>
// Get ALL the errors in a group and assign them to the scope
$scope.errors = ErrorLookup.errors('MainCtrl');
// $scope.errors.user
// $scope.errors.password
// $scope.errors.repeat
// $scope.errors.fullname
// $scope.errors.email
// <div ng-repeat="error in errors.user() track by error.message"></div>
// plucking just a few members
$scope.errors = ErrorLookup.errors('MainCtrl', ['user','password']);
// $scope.errors.user()
// $scope.errors.password()
// or the controller-bound preferred way
this.error = ErrorLookup.error('group', 'full.qualified.modelname.as.written.in.ng-model');
}
]);ErrorLookup.error(group, modelIdentifier, predefine) return a function that has the following signature function(extra).
Effectively, you can trigger new errors without the error being present on the model, like when you return validation from the server, without using model.$setValidity.
$http.post('/isValid', {type: 'email', email: $scope.email}).success(function(errors){
if (errors !== false) {
$scope.error(errors); // assuming errors = {'blacklist': true, 'required': true}
// will look for default blacklist and required messages
// if you assign an string, it will be shown instead of the predefined messages
$scope.error({
'blacklist': 'You failed to enter your email, {{ $value }} even make sense to you? You dirty spammer'
}); // $interpolates this on the fly, not healthy for performance, beware
}
});But wait! You don't need to add an string that will be interpolated, you can use a function! ...Here be dragons...
ErrorLookup.messages.add('dynamic', function(model){
// model is the programmatically equivalent of the scope variables in your interpolated string above
// "this" context is the internal "model"
if (model.$group === 'login') {
return 'Login failed';
} else if (model.$group === 'another') {
return 'Some shit happened';
}
// You must return an string here. Interpolate if you want, ErrorLookup don't care
return 'You failed';
});So let the clusterfuck ensue! Break ALL the conventions! Access ALL the models! Pass ALL elements to callbacks! Wreck ALL the declarative behavior!
Queue a message to be lazy initialized when the ErrorLookup service is instantiated for the first time.
ErrorLookupProvider.add('required','<strong>{{ label }}</strong> is awesome, you gotta fill it', 'html');
ErrorLookupProvider.add('hallelujah','praise almighty code');Remove a message from the queue.
ErrorLookupProvider.remove('required');Returns the interpolated function, shortcut for this.messages[message].
Throws if not defined
ErrorLookup.translate('notrequired'); // throwsCalls $setValidity in the underlaying ngModel manually. Does nothing for forms.
ErrorLookup.validity('group','name', {
required: false,
email: true
}).then(function(errors){
// errors = array
});Calls $validate in the underlaying ngModel manually. If it's a form, it calls $validate() in all
the children.
ErrorLookup.validate('group','name');
// calls ngModel.$validate();ErrorLookup.errors(group: string, pick?: string[], errorArrays: boolean = false, predefine: {}, helpers: boolean = true, reset: boolean = true): {};
Bread and butter, returns an object with all the error messages helpers for a group, or you can pick some manually
Reset forced errors set using ErrorLookup.set() function
ErrorLookup.set(group: string, name: string, errors: {}, reset: boolean = true): QPromise<Errors[]>;
Set programatically an error and return a promise with the updated errors array.
Resets the errors if you specify, sets the model to dirty, and the form to dirty, then forcefully set the errors without updating the ngModel.$errors.
It's a sticky but superficial error, that isn't attached to the ngModel itself.
Usually good to show error forms that come from the server, or manually set errors on inputs without actually making them invalid.
ErrorLookup.set('group','name', {
registered: true, // use the default registered error
domain: 'Domain is invalid' // override the default message
}, true);ErrorLookup.get(group: string, name: string = '', helpers = false, predefined: boolean = false): IErrorHelper;
Return either the whole group, a model, or helpers to save some calls to ErrorLookup.item,
ErrorLookup.error, ErrorLookup.set, ErrorLookup.label, etc
var group = ErrorLookup.get('group', 'helper', true);
/*
returns
{
item: groupHelperModel,
error: Function,
set: (error: any),
label: (item: string, name: string),
reset: (pick: string[]),
validity: (validity: any = {}),
remove: ()
}
*/Set a pretty name for a model, can set many labels at once if you pass an object to the name.
ErrorLookup.label('somegroup', 'login.data.name', 'Login user');
ErrorLookup.label('somegroup', {
'login.data.name': 'Login user',
'login.data.pass': 'Password'
});Returns a function so you can control the error for that field. Executing the returning function returns an array with the errors (or an empty array if none). The errors are kept internally between calls per model.
// fn is Function(Extra: Object|Boolean): Array
var fn = ErrorLookup.error('group','user');
fn({'required':true});
/* returns */
[
{
type:'required',
message:'You must fill user',
label:'user',
name:'user',
item:Model
}
]You can also bypass the current messages that are set for a particular model, making it unique for the same error type
// fn is Function(Extra: Object|Boolean): Array
var fn = ErrorLookup.error('group','user',{'required':'User is sooo required, please fill me in'});
fn({'required':true});
/* returns */
[
{
type:'required',
message:'User is sooo required, please fill me in',
label:'user',
name:'user',
item:Model
}
]And you can bypass the bypass!
// fn is Function(Extra: Object|Boolean): Array
var fn = ErrorLookup.error('group','user',{'required':'User is sooo required, please fill me in'});
fn({'required':'w00t'});
/* returns */
[
{
type:'required',
message:'w00t',
label:'user',
name:'user',
item:Model
}
]Returns an object with all the error functions from above. If you define an array in pick, you can retrieve only some members of the group.
var errors = ErrorLookup.errors('group',['user','email']); // returns {'user':ErrorGetterFunction,'email':ErrorGetterFunction}
errors.user(); // [{type:'required'...}]setting arrays to true returns the current errors array:
var errors = ErrorLookup.errors('group', ['user','email'], true); // returns {'user':Array,'email':Array}
errors.user; // [{type:'required'...}]
// the ErrorLookup.error() must be called somewhere for this array to be filledYou can override the default errors of a group:
var errors = ErrorLookup.errors('group', [], false, {'required':'w00b'}); // returns {'user':ErrorFunction,'email':ErrorFunction,'password':ErrorFunction}
errors.email({required: true}); // [{type:'required','message':'w00b'}]
errors.password({required: true}); // [{type:'required','message':'w00b'}]Remove the model from the errors pile
ErrorLookup.remove(scope.$id, 'user');
ErrorLookup.remove('whole group'); // warning, remove the entire groupThis method is boring as hell. Long parameter list and you shouldn't need to call it manually if you use the directives. You need to always provide non-optional stuff everytime to the function or it breaks.
The config object is as following:
config.scope: the current scope. [Not Optional]config.name: the name of the ng-model, or any internal name you want to use. it must exist in the given scope [Not Optional]config.el: assign a DOM element to the current model [Not optional]config.group: the group name [Not optional]config.controller: the model itself ngModelController (or ngFormController if you add a form model to it) [Not Optional]config.isForm: is the current controller FormController?config.attrs: the $attrs of the element, you can pass an object too when not adding from inside a directiveconfig.label: the label to give the error. Defaults to the name of the model. pretty name for yourlogin.data.userasYour usernamefor exampleconfig.parent: set another ErrorLookup model as parent (not controllers!)
/* ... */
.directive('blah', ['ErrorLookup', function(ErrorLookup){
return {
require:'ngModel',
link: function($scope, el, attr, ctrl){
ErrorLookup.add({
scope : $scope,
group : $scope.$id,
name : attr.ngModel,
controller : ctrl,
el : el
});
}
}
}]);Keeps your application wide messages in a repository
Adds a message. Accepts a function (callback!) or a interpolated string. If you set trustedContext to 'html'
it will use the $sce service and accept safe HTML in your interpolated string.
ErrorLookup.messages.add('required', '<span class="well">You need to fill this field</span>', 'html');Returns the current $interpolated string or the function you passed, you can call it right way.
Remove a message from the service
ErrorLookup.messages.remove('required'); // all "required" error messages, will be silently skipped when this error is present on ngModel =(Loads a JSON representation of your messages. Returns a promise. If you modify the resulting value, you can modify the included messages
ErrorLookup.messages.include('/messages.json').then(function(messages){
delete messages['required'];
});The error-lookup directive will add any ng-model element to the bunch.
By default, error-lookup group elements by scope.$parent.$id, but you can set your
own name using error-lookup="othergroup" (it's preferable this way, so you can reuse in
your code and set errors from inside services and other directives)
The name of the model will be your error-lookup-name, then name attribute, then your ng-model,
in this order.
error-lookup-label can apply a nice name to your model, like error-lookup-label="Your email".
<!-- add this ngModel to our ErrorLookup service -->
<input
ng-model="model.email"
error-lookup-label="your email"
error-lookup="login.interface"
error-lookup-name="email"
type="email"
required
>
<!-- error-lookup-label changes the $label variable -->
<!-- error-lookup-name overrides your ng-model and name attributes -->
<!-- You can, inside your controller, now use
ErrorLookup.get('login.interface','email'), and
even have access to this element lol, breaking
conventions since 2014
-->
<!-- Display some nasty errors to the user, only from
login.interface and email model -->
<ol error-lookup-display="email" error-lookup-group="login.interface">
<li>{{ $latest.message }}</li> <!-- only the latest error in the stack -->
<li>{{ $first.message }}</li> <!-- only the latest error in the stack -->
<li ng-bind-html="$firstHtml"></li> <!-- only the latest error in the stack -->
<li ng-bind-html="$latestHtml"></li> <!-- only the latest error in the stack -->
<li ng-repeat="error in $errors track by $index">{{error.message}}</li> <!-- or show ALL the errors -->
<!-- you can even make your shit clickable -->
<li ng-repeat="error in $errors track by $index" ng-click="myWorldController.click(error)" ng-bind-html="error.message"></li>
<li>Shit! {{ $errorCount }} errors!</li>
</ol>This one is for forms, they keep all their children in sync (long missing from angular itself).
<!-- you can put it on forms, you can display errors for your form as a whole -->
<form error-lookup-form="group" name="fuck">
<input ng-model="doh" error-lookup="another-group">
<input ng-model="srsly" error-lookup="another-group">
<input ng-model="input" error-lookup="another-group">
<div
error-lookup-group="group"
error-lookup-display="fuck"
error-lookup-template="{filter:['form','only','errors'],exclude:['required']}"
></div>
<!-- show all errors for all form models on one place -->
</form>The error-lookup-display is a shortcut to the ErrorLookup.error() function.
This directive exposes to the DOM the following scope variables:
The ErrorLookup model
Current error count
Is first error for that field, containing the fields described in ErrorLookup.error()
Is the top most error for that field, containing the fields described in ErrorLookup.error()
Current cached array of errors
If the field has errors AND is $dirty AND has been $touched
N.B: Since the scope isn't isolated, but a child scope, it inherits from the current scope it's in, make sure to understand scope inheritance before you try your hax0rs in the code.
The $sce.trustAsHtml version of $latest
The $sce.trustAsHtml version of $first
This directive creates a ul with a default limit of 1 item for errors.
It needs to be applied in the same element that has error-lookup-display on it.
<div
error-lookup-display="models.email"
error-lookup-template="{filter: ['generic','someothererror', $variable], 'exclude':['required'], limit: 10}"
>
<!-- setting `filter` will only show `generic`, 'someothererror' and something assigned to the scope $variable,
error messages -->
<!-- setting `limit` will limit the number of messages displayed at once -->
<!-- setting `exclude` won't show errors -->
<!-- all options are optional, they default to none and 1 respectively -->
</div>It's used to filter error messages from a bunch of items in an array,
used by the error-lookup-template directive:
<div error-lookup-display="name">
<div ng-repeat="error in $errors | errorMessages:$options">{{ error }}</div>
</div>