1.0.1 • Published 4 years ago

compose-validators v1.0.1

Weekly downloads
6
License
MIT
Repository
github
Last release
4 years ago

compose-validators

Composable JavaScript validators

Install

with npm:

npm install compose-validators

or yarn:

yarn add compose-validators

API Docs

Why

npm contains several popular packages that perform different kinds of validations. But none of them provides clean and composable functions that can be used as validators. Some of them invent their own domain-specific languages, forcing you to learn custom syntax. Others require you to dive deep into JSON schemas and don't give you clean output.

This library is an attempt to solve these problems. It is focused on

  • Composition. In compose-validators everything is a validator, so you can compose your validators to get more complex ones while having the same API everywhere.
  • Type safety. It is written in TypeScript meaning that you get your validators being statically typed out of the box.
  • Small size. We want the library to be as lightweight as possible while keeping the source code readable. Also, it has zero runtime dependencies. It's now 729 bytes according to size-limit.

Concepts

Validator

Every validator is a function that accepts a value to be validated and returns a validation result.

Validation result

Validation result is always a plain object with collected validation errors. If the object is empty it means the value is valid.

Having validation result as an object allows us to combine results from composed validators like object or arrayOf. This way you can nest your objects and arrays and therefore validate deep structures, like the following example:

import { object, string, required, compose } from "compose-validators";

const validator = object({
  name: compose(string, required),
  address: object({
    city: compose(string, required),
  }),
});

validator({
  name: "John Doe",
  address: {
    city: "",
  },
});

Applying this validator to an object with address.city being an empty string, you will get the following validation result:

{
  "address": {
    "city": {
      "required: true
    }
  }
}

This validation result is non deterministic about your actual error messages, it does not deal with any sort of i18n, though provides enough information for you to display a clean error message.