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

schema.js

v0.1.2

Published

A schema validation and filtering framework

Downloads

9

Readme

schema.js

A schema validation and filtering framework for node.js
It's a fork of conform.js which extends him with $ref option.

Example

The core of schema.js is simple and succinct: validator.validate(obj, schemaId) or simply validator.validate(obj, schema):

  var validator = require('schema.js').validator;

  var schema = {
    properties: {
      url: {
        description: 'the url the object should be stored at',
        type: 'string',
        pattern: '^/[^#%&*{}\\:<>?\/+]+$',
        required: true
      },
      challenge: {
        description: 'a means of protecting data (insufficient for production, used as example)',
        type: 'string',
        minLength: 5
      },
      body: {
        description: 'what to store at the url',
        type: 'any',
        default: null
      },
      address: {$ref: '#nested'}
    }
  };

  validator.add(schema, '#my_schema');

  validator.add({
    properties: {
      town: {type: 'string'},
      city: {type: 'string'},
      country: {type: 'string'}
    }
  }, '#nested');

  console.dir(validator.validate(someObject, '#my_schema'));
  console.dir(validator.validate(someObject, schema));

This will return with a value indicating if the obj conforms to the schema. If it does not, a descriptive object will be returned containing the errors encountered with validation.

  {
    valid: true // or false
    errors: [/* Array of errors if valid is false */]
  }

Installation

Installing schema.js

  $ npm install schema.js

Usage

validator takes json-schema as input to validate objects.

validator.validate (obj, schema, options)

This will return with a value indicating if the obj conforms to the schema. If it does not, a descriptive object will be returned containing the errors encountered with validation.

{
  valid: true // or false
  errors: [/* Array of errors if valid is false */]
}

Available Options

  • validateFormats: Enforce format constraints (default true)
  • validateFormatsStrict: When validateFormats is true treat unrecognized formats as validation errors (default false)
  • validateFormatExtensions: When validateFormats is true also validate formats defined in validate.formatExtensions (default true)
  • cast: Enforce casting of some types (for integers/numbers are only supported) when it's possible, e.g. "42" => 42, but "forty2" => "forty2" for the integer type (default false)
  • castSource: Apply casting (see cast option above) to source object (default false)
  • additionalProperties: Default value for object additionalProperties attribute (default true)
  • applyDefaultValue: Apply value of default attribute to source object (default false)
  • validateDefaultValue: If true value of default attribute will be checked to conforms schema (default false)
  • exitOnFirstError: If true validation will be stopped after first error occurred, valid will be false and errors will contain single error (default false)
  • failOnFirstError: Like exitOnFirstError option but error will be thrown, property info of error will contain regular validation error information (default false)

Notice: all options (such as castSource, additionalProperties) as well as attributes (such as filter) which modifies source object do that directly and immediately. That means that if some property (e.g. property1) was modified but later, on other property (e.g. property2), validation or filtering fails source object will be with modified property1 despite on valid equals to false at result.

Schema

For a property an value is that which is given as input for validation where as an expected value is the value of the below fields

required

If true, the value should not be empty

{ required: true }

type

The type of value should be equal to the expected value

{ type: 'string' }
{ type: 'number' }
{ type: 'integer' }
{ type: 'array' }
{ type: 'boolean' }
{ type: 'object' }
{ type: 'null' }
{ type: 'any' }
{ type: ['boolean', 'string'] }

pattern

The expected value regex needs to be satisfied by the value

{ pattern: /^[a-z]+$/ }

maxLength

The length of value must be greater than or equal to expected value

{ maxLength: 8 }

minLength

The length of value must be lesser than or equal to expected value

{ minLength: 8 }

minimum

Value must be greater than or equal to the expected value

{ minimum: 10 }

maximum

Value must be lesser than or equal to the expected value

{ maximum: 10 }

exclusiveMinimum

Value must be greater than expected value

{ exclusiveMinimum: 9 }

exclusiveMaximum

Value must be lesser than expected value

{ exclusiveMaximum: 11 }

divisibleBy

Value must be divisible by expected value

{ divisibleBy: 5 }
{ divisibleBy: 0.5 }

minItems

Value must contain more then expected value number of items

{ minItems: 2 }

maxItems

Value must contains less then expected value number of items

{ maxItems: 5 }

uniqueItems

Value must hold a unique set of values

{ uniqueItems: true }

enum

Value must be present in the array of expected value

{ enum: ['month', 'year'] }

format

Value must be a valid format

{ format: 'url' }
{ format: 'email' }
{ format: 'ip-address' }
{ format: 'ipv6' }
{ format: 'date-time' }
{ format: 'date' }
{ format: 'time' }
{ format: 'color' }
{ format: 'host-name' }
{ format: 'utc-millisec' }
{ format: 'regex' }

conform

Value must conform to constraint denoted by expected value

{ conform: function (v, o) {
    // `o` is current object at validation
    if (v%3==1) return true;
    return false;
  }
}

dependencies

Value is valid only if the dependent value is valid

{
  town: { required: true, dependencies: 'country' },
  country: { maxLength: 3, required: true }
}

filter

Apply filter on value

{
  filter: function (v) {
    return v.toLowerCase();
  }
}

filter attribute can be array of filters.
Filter applies only after successful validation of value.
Filter errors as validation errors sets valid to false and provides error description at errors array.
Complex types (array, object) can't be filtered directly, use filter for array items or object properties instead.

$ref

You can add links to nested schemas, already loaded in validator, or use links to schema itself $ref: '#'.

{
  properties: {
    nested: {$ref: '#nested'},
    itself: {$ref: '#'}
  }
}

Nested Schema

We also allow nested schema

{
  properties: {
    title: {
      type: 'string',
      maxLength: 140,
      required: true
    },
    author: {
      type: 'object',
      required: true,
      properties: {
        name: {
          type: 'string',
          required: true
        },
        email: {
          type: 'string',
          format: 'email'
        }
      }
    }
  }
}

Custom Messages

We also allow custom message for different constraints

{
  type: 'string',
  format: 'url'
  messages: {
    type: 'Not a string type',
    format: 'Expected format is a url'
  }
{
  conform: function () { ... },
  message: 'This can be used as a global message'
}

Tests

Clone repository from github, cd into cloned dir and install dev dependencies

  $ npm install

run tests

  $ npm test

conform.js author: Oleg Korobenko

revalidator authors: Charlie Robbins, Alexis Sellier

revalidator contributors: Fedor Indutny, Bradley Meck, Laurie Harper

License: Apache 2.0