Another biased type checking solution for Javascript.
Exception messages may change between patch versions, as often the patch will change some behaviour that was unexpected and naturally it results in a different error message.
// use precompiled primitives for high performancetypeforce(typeforce.Array, array)// or just precompile a templatevar type = { foo: 'Number', bar: '?String'}var fastType = typeforce.compile(type)// fastType => typeforce.object({// foo: typeforce.Number,// bar: typeforce.maybe(typeforce.String)// })// use strictness for recursive types to enforce whitelisting propertiestypeforce({ x: 'Number'}, { x: 1 }, true)// OK!typeforce({ x: 'Number'}, { x: 1, y: 2
Protips (extended types):
typeforce(typeforce.tuple('String', 'Number'), ['foo', 1])// OK!typeforce(typeforce.tuple('Number', 'Number'), ['not a number', 1])// TypeError: Expected property "0" of type Number, got String 'not a number'typeforce(typeforce.map('Number'), { 'anyKeyIsOK': 1})// OK!typeforce(typeforce.map('Number', typeforce.HexN(8)), { 'deadbeef': 1, 'ffff0000': 2})
Protips (no throw)
var typeforce = require('typeforce/nothrow')var value = 'foobar'if (typeforce(typeforce.Number, value)) { // didn't throw! console.log(`${value} is a number`) // never happens} else { console.log(`Oops, ${typeforce.error.message}`) // prints 'Oops, Expected Number, got String foobar'}
Protips (async)
var typeforce = require('typeforce/async')typeforce(typeforce.Number, value, function (err) { if (err) return console.log(`Oops, ${typeforce.error.message}`) console.log(`${value} is a number`) // never happens})
WARNING: Be very wary of using the quacksLike type, as it relies on the Foo.name property.
If that property is mangled by a transpiler, such as uglifyjs, you will have a bad time.