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

mongo-why

v0.0.1

Published

Tells you why mongodb fails to validate your document

Downloads

37

Readme

mongo-why Build Status

Tells you why mongo fails to validate your document.

In a project of Appier, we use mongodb validator as a "schema". However, as the "schema" grows, it is a pain to see which part of a document fails validation. why.js is a library that can be loaded inside mongo shell and provides a function called why(), which shows a list of validator rules that the doc has violated.

Use case

Load why.js into mongo shell, then use why(<name of collection>, <the document you want to insert>)

$ mongo --shell path/to/why.js
MongoDB shell version: 3.2.4
type "help" for help
> why('users', {name: 123})
-------------------------
Unmatched validator rules
-------------------------
[
  {
    "name": {
      "$type": "string"
    }
  },
  {
    "password": {
      "$exists": true
    }
  }
]

Under the hood, it applies parts of the specified collection's validator to a temporary collection, and tries inserting the document into that temporary collection. Then it prints out the parts of the validator that cannot validate the document.

You may also specify a validator directly:

$ mongo --shell path/to/why.js
MongoDB shell version: 3.2.4
type "help" for help
> validator = {name: {$type: 'string'}, password: {$exists: true}}
> why(validator, {name: 123})
-------------------------
Unmatched validator rules
-------------------------
[
  {
    "name": {
      "$type": "string"
    }
  },
  {
    "password": {
      "$exists": true
    }
  }
]

Options

The third argument for why() is for options. The options hash and their default value are as follows:

why('CollectionName', documentToTest, {
  // when true, it returns unmached validator rules as arrays instead of printing
  // them out, so that you can customize the error output
  //
  quiet: false,
})

Development

There is only one file, why.js, a script that runs in mongo shell. It only has limited ES2016 support, this should be taken into account during development.

Unit Test

$ mongo test.js
MongoDB shell version: 3.2.4
connecting to: test
# If there is no assertion errors, the test passes.