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

respect

v0.2.3

Published

Comparison plugin for BDD assertion libraries (chai, should)

Downloads

2,854

Readme

respect.js

Build Status

Comparison plugin for BDD assertion libraries (chai, should)

Installation

In node.js:

$ npm install respect --save-dev

In the browser

<script src="respect.min.js" type="text/javascript"></script>

tl;dr

The philosophy behind respect.js is to extend BDD assertions to make quick and comprehensive object comparisons. It extends should-like assertions with a respect method that takes a specification and checks it matches.

var record = {
  _id: '5515ce73959470012aef024a',
  name: 'Eva Warner',
  age: 23,
  lastLogin: new Date('2014-05-20 07:51:36'),
  particularity: 'Matches this Regex',
  nestedObj: {
    nestedArray: [5, '34', null, true]
  },
  anotherArray: [{
    willBeChecked: true
  }, {
    willBeChecked: false
  }],
  other: 'Not relevant, will be ignored in the test'
};
record.should.respect({
  name: 'Eva Warner',
  age: function(age) {
    return (age >= 7) && (age <= 77);
  },
  lastLogin: Date,
  particularity: /regex/i,
  nestedObj: {
    nestedArray: [5, String, null, Boolean]
  },
  anotherArray: {
    0: {
      willBeChecked: true
    },
    length: 2
  },
  unexpectedPropertyThatShouldNotBeHere: undefined
});

This flexible approach can make data-comparing unit-tests less heavy and more expressive, especially when it comes to database documents for instance:

  • no need to omit/pick fields before a deep comparison because they are irrelevant or unpredictable (ids, dates...)
  • easy-to-write one-shot comparison that can check an equality, but also a regex match or a constructor...

In one words, it checks if an object respects a specification rather than comparing two objects.

API

Declaration

var respect = require('respect');

With should

var should = require('should');
should.use(respect.shouldPlugin());

With chai

var chai = require('chai');
chai.use(respect.chaiPlugin());

// Then, according to your preferences:
var should = chai.should();
// OR
var expect = chai.expect;

Assertions

The generic syntax is:

data.should.respect(specifications, options);
// OR
expect(data).to.respect(specifications, options);

Nested objects are compared recursively, and arrays are iterated over. options can be omitted: by default all the following options are set to true:

partial: Ignore un-specified fields

var record = {
  notImportant: 'It is here but we do not need to check for it'
};
record.should.respect({
  butThisFieldShouldBeAbsent: undefined
});

Note: if the record object does have the butThisFieldShouldBeAbsent field, an exception will be raised.

This behaviour can be deactivated by providing a { partial: false } option.

regex: Regex shortcuts

var record = {
  uuid: 'bbd4e20b-cdd4-5107-ad63-02a2cfc23c5b'
};
record.should.respect({
  uuid: /^[A-Z0-9]{8}-[A-Z0-9]{4}-[A-Z0-9]{4}-[A-Z0-9]{4}-[A-Z0-9]{12}$/i
});

This behaviour can be deactivated by providing a { regex: false } option.

types: Constructors shortcut

var record = {
  name: 'John',
  age: 55,
  now: new Date(),
  pattern: /[aA]bc.\s/,
  dateConstructor: Date,
  regexConstructor: RegExp
};
record.should.respect({
  name: String,
  age: function(age) {
    return (age >= 7) && (age <= 77);
  },
  now: Date,
  pattern: RegExp,
  dateConstructor: Date,
  regexConstructor: RegExp
});

This behaviour can be deactivated by providing a { types: false } option.

lambdas: Lambda evaluation functions shortcut

var record = {
  name: 'John',
  age: 55
};
record.should.respect({
  name: 'John',
  age: function(age) {
    return (age >= 7) && (age <= 77);
  }
});

This behaviour can be deactivated by providing a { lambdas: false } option.

Override default behaviours

On the assertion level:

Example of changing default behaviours:

// will raise assertion multiple errors because of options
var record = {
  description: 'matches the regex but is a string',
  now: new Date(),
  fieldThatShouldNotBeHere: true   // will not be accepted because partial=false
};
record.should.respect({
  description: /regex/,            // will fail because regex=false
  now: Date                        // will fail because types=false
}, {
  partial: false,
  regex: false,
  types: false
});

In this extreme example, every option is removed so the comparison ends up to a deep equal. Whereas it can be necessary to deactivate one given behaviour for specific cases, it is silly to use respect in place of a deep equal comparator. Just use the already implemented should.deep.equal.

On the plugin level

chaiPlugin and shouldPlugin both accept an options object, which can override the default behaviours for all assertions made from this module. Besides, for those who prefer to use their own keyword instead of the default 'respect', you can easily pick your own alias by providing an alias option when generating the plugin. You can even declare several plugins with different options under different aliases.

var chai = require('chai');
var respect = require('respect');
chai.use(respect.chaiPlugin({ alias: 'matchStrictly', partial: false, types: false }));
chai.use(respect.chaiPlugin({ alias: 'matchAll', partial: false }));
chai.use(respect.chaiPlugin({ alias: 'matchPartially' }));
chai.should();

var record = {
  name: 'Jimmy Hudson',
  age: 54,
  male: true
};

// Will fail because of the unactivated `types` option
record.should.matchStrictly({ name: String, age: Number, male: Boolean });

// Will fail because of the unactivated `partial` option and the missing 'male' key
record.should.matchAll({ name: String, age: Number });

// Will succeed
record.should.matchPartially({ name: String, age: Number });

Extend the comparison methods

var Comparator = require('respect');
var MyComparator = // TODO write extension code (examples to come)
chai.use(MyComparator.chaiPlugin());

Comparisons outside of BDD assertions

If you want to use respect as a comparison util outside of BDD assertions, you can simply use its check() method.

// respect.check(actual, expected, [options])
var record = {
  name: 'Darth Vader',
  badass: true
};
respect.check(record, { badass: true });                      // true
respect.check(record, { badass: true }, { partial: false });  // false

Tests

$ npm test

Documentation

$ npm run gen-doc

License

MIT License Copyright (c) 2015 Sabiwara