npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

specification

v0.1.0

Published

Node implementation of the specification pattern

Downloads

46

Readme

Specification pattern for NodeJS

Specification pattern implementation for NodeJS. Suitable for any kind of validations, simplifying, improving reusability and and making code clearer.

Although the specification pattern is mainly use in DDD to check business rules, I the idea of combine rules offers great flexibility.

This is a JavaScript implementation of the pattern, both synchronous and asynchronous versions, so you can create your custom validation rules and combine them easily into a new rule.

How to use ?

First step is to include the required version (synchronous or asynchronous):

// Asynchronous version
var specification = require("specification").Specification;

// Synchronous version
var specificationSync = require("specification").SpecificationSync;

For each business rule (or validation) you need to check, a specification must be created. Next code creates a specification that checks if a number is greater than the one indicated at the specification:

function GreaterThan(num) {
  this.num = num;
}
// Make it a subclass of SpecificationSync base class.
GreaterThan.prototype = Object.create(SpecificationSync);

// Implement the 'isSatisfiedBy' method.
GreaterThan.prototype.isSatisfiedBy = function(n) {
  return (n > this.num);
};

Later, to use the previous specification:

var greaterThan6 = new GreaterThan(6);

if (greaterThan6.isSatisfiedBy(9)) {
  console.log("9 is greater than 6");
}

The base class SpecificationSync offers the and, or and not methods we can use to chain specifications and build complex ones. For example:

var greaterThan6 = new GreaterThan(6);
var greaterThan8 = new GreaterThan(8);

var greaterThan6And8 = greaterThan6.and(greaterThan8);

if (greaterThan6And8.isSatisfiedBy(9)) {
  console.log("9 is greater than 6 and 8");
}

The asynchronous version is suitable if you need to check agains an asynchronous source, like a database, files, etc. The only difference is the way to implement the isSatisfiedBy() method, which must be use a callback, for example:

function GreaterThan(num) {
  this.num = num;
}
GreaterThan.prototype = Object.create(Specification);
GreaterThan.prototype.isSatisfiedBy = function(n, cb) {
  return cb(null, n > this.num);
};

and to use it you can make via the callback:

var greaterThan6 = new GreaterThan(6);

greaterThan6.isSatisfiedBy(9, function(err, satisfies) {
  if (satisfies) {
    console.log("9 is greater than 6");
  }
});

Chaining specifications works in the same way as the synchronous version, simply remember the only difference is the way to use the isSatisfiedBy() method:

new GreaterThan(1)
  .and(new GreaterThan(2))
  .and(new GreaterThan(3))
  .isSatisfiedBy(6, function(err, satisfies) {
    if (satisfies) {
      console.log("6 is greater than 1, 2 and 3");
    }
  });

The MIT License (MIT)

Copyright (c) 2015 Antonio Santiago (@acanimal)

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.