Skip to content
Commits on Apr 13, 2015
  1. Merge pull request #34 from nfroidure/patch-1

    committed
    Update README.md
  2. @nfroidure

    Update README.md

    nfroidure committed
Commits on Dec 20, 2014
  1. minor.

    committed
  2. minor.

    committed
  3. minor.

    committed
Commits on Dec 19, 2014
  1. level bump, fixed bug.

    committed
  2. fixed bug: validate would catch error if a callback is supplied which…

    committed
    … throws an error, and might also call the callback twice (issue #24)
Commits on Jan 24, 2013
  1. level bump

    committed
  2. level up

    committed
  3. Merge pull request #19 from feugy/master

    committed
    Union type not supported at highest level
  4. @feugy
Commits on Jan 21, 2013
  1. @feugy
  2. @feugy
Commits on Jan 8, 2013
  1. added support for comma decimal sign in date-time format.

    unknown committed
    added tests for date-time format with decimal fractions.
    added contributors.
  2. Merge pull request #16 from NicolasPelletier/timeFixBranch

    committed
    Updated date-time format acceptance criteria to allow decimal fraction.
  3. Merge pull request #15 from NicolasPelletier/master

    committed
    Remove the restriction on top-level schema type.
  4. Update date-time format acceptance criteria.

    Nicolas Pelletier committed
    According to ISO8601 spec (http://en.wikipedia.org/wiki/ISO_8601#Times),
    the time can include fractions.
    
    The JSON schema spec ( draft 3 ) recommends but does not force the
    following ISO8601 format: YYYY-MM-DDThh:mm:ssZ.
    
    Since a javascript Date object includes the milliseconds when converted
    into a string with method toISOString(), I thought easier to accept the
    string with the milliseconds in the JSON Schema. The code was modified
    to accept but not force the presence of a 'dot' and then an unspecified
    number of digits representing the fraction of a second.
    
    I ran the test suite and nothing failed.
  5. Remove the restriction on schema type.

    Nicolas Pelletier committed
    The validation of the schema itself restricted the type of the root
    object of the schema to an 'object' or an 'array'. This means that
    the following schema would be rejected:
      {
        type: 'null',
        description: 'Nothing is returned.'
      }
    
    This fix removes this limitation.
    
    Also updated the test suite following the change in requirement
    for the root type of a schema.
    
    (Also added a semi-colon missing at the end of a line...)
  6. Added the MIT license.

    committed
  7. Added the MIT license.

    committed
  8. Added the MIT license.

    committed
    go ahead, use it!
  9. Merge pull request #14 from jessejlt/patch-1

    committed
    Fix leak and multiply defined variable
Commits on Dec 9, 2012
  1. @jessejlt

    Fix leak and multiply defined variable

    jessejlt committed
    Variable `prop` was leaking, and `property` was multiply defined and was being used outside of various scopes. 
Commits on Nov 7, 2012
  1. minor

    committed
  2. minor

    committed
  3. version up

    committed
Something went wrong with that request. Please try again.