JSPM

  • Created
  • Published
  • Downloads 22048
  • Score
    100M100P100Q154484F
  • License BSD-3-Clause

Ember computed property based validations

Package Exports

  • ember-cp-validations
  • ember-cp-validations/htmlbars-plugins/v-get

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (ember-cp-validations) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Ember CP Validations

Gitter Build Status npm version Code Climate Test Coverage Ember Observer Score Dependency Status devDependency Status

A Ruby on Rails inspired model validation framework that is completely and utterly computed property based.

Features

No observers were used nor harmed while developing and testing this addon.

  • Lazily computed validations
  • Ruby on rails inspired validators
  • Support for both Ember Data Models and Objects
  • Synchronous and asynchronous support for both validators and validations
  • Dirty tracking
  • Support for nested models via belongs-to and hasMany relationships
  • No observers. Seriously... there are none. Like absolutely zero....
  • Meta data based cycle tracking to detect cycles within your model relationships which could break the CP chain
  • Custom validators
  • Ember CLI generator to create custom validators with a unit test
  • I18n support

Installation

ember install ember-cp-validations

Changelog

Changelog can be found here

Upgrading from 1.x to 2.x

There are some breaking changes so to make the process of upgrading as smooth as possible, we wrote up some upgrade documentation. If you face any issue, please feel don't hesitate to open an issue.

Documentation

Detailed documentation can be found here

Live Demo

A live demo can be found here

Looking for help?

If it is a bug please open an issue on GitHub.

Basic Usage - Models

The first thing we need to do it build our validation rules. This will then generate a Mixin that you will be able to incorporate into your model or object.

// models/user.js

import Ember from 'ember';
import DS from 'ember-data';
import {
  validator, buildValidations
}
from 'ember-cp-validations';

var Validations = buildValidations({
  username: validator('presence', true),
  password: [
    validator('presence', true),
    validator('length', {
      min: 4,
      max: 8
    })
  ],
  email: [
    validator('presence', true),
    validator('format', { type: 'email' })
  ],
  emailConfirmation: [
    validator('presence', true),
    validator('confirmation', {
      on: 'email',
      message: 'do not match',
      description: 'Email addresses'
    })
  ]
});

Once our rules are created and our Mixin is generated, all we have to do is add it to our model.

// models/user.js

export default DS.Model.extend(Validations, {
  'username': attr('string'),
  'password': attr('string'),
  'email': attr('string')
});

Basic Usage - Objects

You can also use the generated Validations mixin on any Ember.Object or child of Ember.Object, like Ember.Component. For example:

// components/x-foo.js

import Ember from 'ember';
import {
  validator, buildValidations
}
from 'ember-cp-validations';

var Validations = buildValidations({
  bar: validator('presence', true)
});

export default Ember.Component.extend(Validations, {
  bar: null
});

To lookup validators, container access is required which can cause an issue with Ember.Object creation if the object is statically imported. The current fix for this is as follows.

// models/user.js

export default Ember.Object.extend(Validations, {
  username: null
});

Ember < 2.3.0-beta.1

// routes/index.js

import User from '../models/user';

export default Ember.Route.extend({
  model() {
    var container = this.get('container');
    return User.create({ username: 'John', container })
  }
});

Ember >= 2.3.0-beta.1

// routes/index.js

import User from '../models/user';

export default Ember.Route.extend({
  model() {
    var options = { username: 'John' };
    Ember.setOwner(options, Ember.getOwner(this));
    return User.create(options)
  }
});

Advanced Usage

Default Options

Default options can be specified over a set of validations for a given attribute. Local properties will always take precedence.

Instead of doing the following:

var Validations = buildValidations({
  username: [
    validator('presence', {
      presence: true,
      description: 'Username'
    }),
    validator('length', {
      min: 1,
      description: 'Username'
    }),
    validator('no-whitespace-around', {
      description: 'A username'
    })
  ]
});

We can declare default options:

var Validations = buildValidations({
  username: {
    description: 'Username'
    validators: [
      validator('presence', true),
      validator('length', {
        min: 1
      }),
      validator('no-whitespace-around', {
        description: 'A username'
      })
    ]
  },
});

In the above example, all the validators for username will have a description of Username except that of the no-whitespace-around validator which will be A username.

Options as Functions

All options can be functions which are processed lazily before validate is called. These functions have the context of the validator that is being executed, giving you access to all its properties such as options, model, attribute, etc.

Please note that the message option of a validator has its own signature.

var Validations = buildValidations({
  dob: validator('date', {
    description: 'Date of Birth',
    format() {
      return this.get('model.meta.date.format');
    },
    before() {
      return moment();
    },
    after() {
      return moment().subtract(120, 'years');
    }
  })
});