Permalink
Commits on Jan 4, 2017
  1. 0.1.7

    dresende committed Jan 4, 2017
  2. Merge pull request #7 from kevpie/long_email_tld

    dresende committed Jan 4, 2017
    Expand TLD validation size to 63 for long gTLD.
Commits on Jan 3, 2017
Commits on Mar 4, 2015
  1. 0.1.6

    dresende committed Mar 4, 2015
  2. Merge pull request #5 from x64x6a/master

    SPARTAN563 committed Mar 4, 2015
    Removed console logging from security module (js)
Commits on Feb 25, 2015
  1. Removed console info

    x64x6a committed Feb 25, 2015
Commits on Apr 26, 2014
  1. 0.1.5

    dresende committed Apr 26, 2014
  2. Fixes initial patterns tests

    dresende committed Apr 26, 2014
  3. Adds enforce.patterns.ipv6()

    dresende committed Apr 26, 2014
  4. 0.1.4

    dresende committed Apr 26, 2014
  5. Adds enforce.patterns.mac()

    dresende committed Apr 26, 2014
  6. 0.1.3

    dresende committed Apr 26, 2014
Commits on Sep 16, 2013
  1. should@1.2.2

    dresende committed Sep 16, 2013
    Reverting should dependency. Similar to what I did in orm, since it's
    failing on v0.6 acording to TravisCI.
Commits on Sep 13, 2013
Commits on Aug 19, 2013
  1. Support legacy check callback with `error: Error`

    SPARTAN563 committed Aug 19, 2013
    Legacy callback system would not present an array of errors to the
    callback unless returnAllErrors was set. Updated the typescript version to
    support this, since removal resulted in breaking of ORM.
  2. Merge pull request #1 from dresende/typescript

    dresende committed Aug 19, 2013
    Switch to TypeScript and allow Validator chaining
Commits on Aug 14, 2013
  1. Add chaining tests

    SPARTAN563 committed Aug 14, 2013
  2. Switch to TypeScript

    SPARTAN563 committed Aug 14, 2013
    Allows us to easily ensure the validity of any code in the library and
    gives users the option of IntelliSense with supporting IDEs.
    
    Also added the ability to chain methods onto validators, with an
    orUndefined() one provided by default. Added tests to ensure that it
    functions as expected, and with minimal modifications to the tests (only
    those necessary to adapt to the new chainable Validator object's API)
    everything functions as expected. External API remains unchanged, except
    for the addition of an `enforce.Validator` object to ease construction
    of custom validators.
    
    I have also added a translator between legacy calls to
    `Enforce.add(property: string, validator: function(value: any, next:
    (errorMessage?: string) => void, contexts?: ContextMap) => boolean);`
    and the new Validator objects to help ensure a smooth transition between
    any software using Enforce already and the new version.
Commits on Aug 12, 2013
  1. 0.1.2

    dresende committed Aug 12, 2013
  2. Adds enforce.security.username(opts = { length: 2 }, msg = "invalid-u…

    dresende committed Aug 12, 2013
    …sername")
    
    It's a symlink to enforce.patterns.match(/^[A-Za-z_][A-Za-z0-9_-]+$/).
Commits on Jul 25, 2013
  1. Adds enforce.security.creditcard(types = [ "amex", "visa", "maestro",…

    dresende committed Jul 25, 2013
    … "discover", "mastercard" ], msg = "not-valid-creditcard")
    
    There's also a fallback type called "luhn" which will only run the luhn
    algorithm.
Commits on Jul 24, 2013
  1. v0.1.1

    dresende committed Jul 24, 2013
  2. Adds context to enforcements

    dresende committed Jul 24, 2013
  3. v0.1.0

    dresende committed Jul 24, 2013
  4. Adds patterns enforcements

    dresende committed Jul 24, 2013