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

validation-codes

v1.0.0

Published

An AMD-module to validate user input both on client and server side returning easily parseable error codes

Downloads

3

Readme

[email protected]

An AMD-module to validate user input both on client and server side returning easily parseable error codes.

Define a validator by combining rules:

eMailValidator = new Rules.ViolationCodeModifier(new Rules.And([new Rules.Existence(), new Rules.Blacklist(),
                                                 new Rules.Email(), new Rules.MaxLength()]), 'Email')

This could be used to return error codes from a server side:

unless eMailValidator.isValid "invalidMail@"
  return res.status(400).send                                              
    errors: eMailValidator.validate email 

Or to render alerts in a Backbone view:

@$(".alert").remove()
if eMailValidator.isValid @$("input").val()
  @$el.removeClass "has-error"
else
  @$el.addClass "has-error"
  for code in eMailValidator.validate @$("input").val()
    @$(".alert-box").prepend alertTemplate
      type: "alert-danger"
      message: @getErrorMessage(code)

API

The module can be required via node's require, or as an AMD module via requirejs. There is a codo created documentation in the doc folder with more details.

Available rules

  • And: Valid if all of its sub-rules are valid
  • Or: Valid if any of its sub-rules is valid
  • Blacklist: Valid if the value is not in a predefined list or undefined
  • Email: Valid if the value confirms the W3C recommendation for email verification (not equivalent to RFC 5322!) or is undefined
  • Existence: Valid if the value exists
  • MaxLength: Valid if the value is at most a maximum length or undefined
  • MinLength: Valid if the value is at least a minimum length or undefined
  • Not: Valid if the sub-rule is invalid
  • Object: Valid if the properties of the value confirm to the sub-rules set for the properties
  • Regex: Valid if the value confirms to a given regex or is undefined
  • ViolationCodeModifier: Valid if the sub-rule is valid. Used to prepend an identifier to the sub rules violation codes.

isValid

Will return true if the object to validate is valid.

validate

Returns an Array with the rules violation code if it is violated.