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

lg-joigoose

v0.0.1

Published

Joi validation for your Mongoose models without the hassle of maintaining two schemas

Downloads

6

Readme

joigoose

npm version Build Status Dependencies Status

Joi and Mongoose sitting in a tree K-I-S-S-I-N-G...

Joi validation for your Mongoose models without the hassle of maintaining two schemas.

Installation

npm install joigoose

Usage

1. Import Mongoose and Joi

We must pass Mongoose into Joigoose so it knows about ObjectIds and other Mongoose specific stuff:

var Mongoose = require('mongoose');
var Joigoose = require('joigoose')(Mongoose);

2. Write your Joi schema (see here about how to specify ObjectIds!)

Things to know!

Mongoose specific options can be specified in the meta object (see below).

Arrays with items of different types will end up with the Mongoose type Mixed. Ideally, Joi schemas shouldn't have to contain Mongoose specific types, such as Mongoose.Schema.Types.ObjectId because these Joi schemas may be required to work on frontend clients too.

var joiUserSchema = Joi.object({
    name: Joi.object({
        first: Joi.string().required(),
        last: Joi.string().required()
    }),
    email: Joi.string().email().required(),
    bestFriend: Joi.string().meta({ type: 'ObjectId', ref: 'User' }),
    metaInfo: Joi.any()
});

3. Convert your Joi schema to a Mongoose-style schema

var mongooseUserSchema = Joigoose.convert(joiUserSchema);

4. Create your model

User = Mongoose.model('User', mongooseUserSchema);

5. Enjoy!

var aGoodUser = new User({
    name: {
        first: 'Barry',
        last: 'White'
    },
    email: '[email protected]',
    metaInfo: {
        hobbies: ['cycling', 'dancing', 'listening to Shpongle']
    }
});

aGoodUser.save(function (err, result) {

    // -> Success!
});

var aBadUser = new User({
    name: {
        first: 'Barry',
        last: 'White'
    },
    email: 'Im not an email address!'
});

aBadUser.save(function (err, result) {

    // -> Error!
    // {
    //     "message": "User validation failed",
    //     "name": "ValidationError",
    //     "errors": {
    //         "email": {
    //             "properties": {
    //                 "type": "user defined",
    //                 "message": "Validator failed for path `{PATH}` with value `{VALUE}`",
    //                 "path": "email",
    //                 "value": "Im not an email address!"
    //             },
    //             "message": "Validator failed for path `email` with value `Im not an email address!`",
    //             "name": "ValidatorError",
    //             "kind": "user defined",
    //             "path": "email",
    //             "value": "Im not an email address!"
    //         }
    //     }
    // }
});

Known Limitations

I didn't spend long writing this, but I've aimed for 100% code coverage. It can be so much better, so help me out! Submit your issues and pull requests on GitHub.

  • No peer based validation (and, nand, or, xor, with, without, ref, assert, alternatives, when etc)
  • No Joi.binary object type
  • No Joi.func object type