Schemawax is a tool for creating typed decoders to help you get to the DNA of your data.
To add schemawax to your project, do:
# NPM
npm install schemawax
# Yarn
yarn add schemawaxIt is only 1.2 kB!
I recommend checking out some examples to get an idea of what this library can do for you. (spoiler: a lot)
You can start in a couple of simple steps!
Build a decoder:
import * as D from 'schemawax'
const userDecoder = D.object({
required: {
name: D.string,
preferredName: D.nullable(D.string),
emailVerified: D.boolean
}
})
// You can get the shape of the data into a type, use D.Output<…>
type User = D.Output<typeof userDecoder>Get your data:
// Usually, you would get the data using 'JSON.parse(response)' or something
const data = {
name: 'Bob',
preferredName: null,
emailVerified: false
}Decode your data:
const parsed = userDecoder.decode(data)
if (parsed) {
console.log(parsed)
} else {
console.log('Failed to decode')
}The decoders are fully typed so you can confidently use your data in TypeScript.
You can either delve into the documentation (highly recommended) or check out some of our quick recipes.
Decoders can consume data through one of these methods:
Decoder.decode tries to decode data and if it fails, it returns null .
This method returns a type of D | null where D is your type. If you do not want to have the null in there, see below.
D.string.decode('a string') // 'a string'
D.array(D.unknown).decode([]) // []
D.array(D.number).decode([1, 2, 3]) // [1, 2, 3]
D.string.decode(42) // null
D.array(D.unknown).decode('not an array') // nullThis one works the same way as the previous one but throws a DecoderError when it fails. You might use it if you want a top-level nullable structure (unlikely) or you just want to throw errors.
This method return a type of D which is the output type of your decoder.
D.string.forceDecode('a string') // 'a string'
D.array(D.unknown).forceDecode([]) // []
D.array(D.number).forceDecode([1, 2, 3]) // [1, 2, 3]
D.string.forceDecode(42) // throws DecoderError
D.array(D.unknown).forceDecode('not an array') // throws DecoderErrorThis method returns true or false based on whether the decoder would fail. It also serves as a type guard.
D.string.is('string') // true
D.string.is(42) // false
// Type guard out of this
const decoder = D.array(D.boolean)
const data = [true, false]
if (decoder.is(data)) {
// TypeScript now knows that data is an array of booleans
data.map(console.log)
} else {
console.log('This is not and array of booleans')
}This method returns a discriminated union based on whether the decoder would fail or pass. It is useful to pattern match on the decoder result, getting the data or error without using a try catch clause.
D.string.validate('a string') // { type: 'ok', data: 'somestringvalue' }
D.string.validate(42) // { type: 'error', error: DecoderError }
// Using it in practice
const decoder = D.array(D.boolean)
const data = [true, false]
const validationResult = decoder.validate(data)
switch (validationResult.type) {
case 'ok':
// TypeScript now knows that result has data which is an array of booleans
validationResult.data.map(console.log)
break;
case 'error':
// TypeScript now knows that result has error so you can log the error message
console.log(validationResult.error.message)
break;
}All primitive decoders work the same
This is a simple decoder: if the input is a string, return the string, else fail (e.g. return null or throw an error).
D.string.decode('a string') // 'a string'
D.string.decode(42) // null
D.string.decode({}) // null
D.string.forceDecode(false) // throws DecoderErrorD.number.decode(42) // 42
D.number.decode('a string') // nullD.boolean.decode(true) // true
D.boolean.decode('not a boolean') // nullLiteral decoder only decodes the exact same value (compared using ===).
D.literal('data').decode('data') // 'data'
D.literal('error').decode('error') // 'error'
D.literal(0).decode(0) // 0
D.literal('data').decode('error') // null
D.literal(0).decode(1) // nullD.literalUnion combines D.literal and D.oneOf the way you would expect.
const decoder = D.literalUnion('data', 'error') // D.Decoder<'data' | 'error'>
decoder.decode('data') // 'data'
decoder.decode('error') // 'error'
decoder.decode('not in there') // nullD.regex checks if a given regular expression matches the data. (This is particularly useful when you want to transform the data afterwards. See andThen)
const decoder = D.regex(/^\d+$/)
decoder.decode('138') // '138'
decoder.decode('Not nice') // nullWith transformation afterwards:
decoder.decode('138').andThen(Number) // 138This decoder tries all the decoders passed to it in order and returns the first one that succeeds.
const decoder = D.oneOf(D.string, D.number)
decoder.decode('a string') // 'a string'
decoder.decode(42) // 42
decoder.decode(false) // nullUsing this you can comfortably decode TS tuples. (for example from JSON arrays)
const minMaxDecoder = D.tuple(D.number, D.number)
const data = JSON.parse('{ "minmax": [18, 99] }')
D.object({ // More on this below
required: {
minmax: minMaxDecoder
}
}) // { minmax: [18, 99] }minmax is now typed as [number, number] and not as number[]
const [firstName, lastName] = D.tuple(D.string, D.string).forceDecode(['Michael', 'Jackson'])
firstName === 'Michael' // true
lastName === 'Jackson' // trueLonger arrays get stripped at the end to fit the length of the tuple. Shorter arrays with not enough elements fail to decode.
The array decoder takes another decoder with which it tries to decode a whole JSON array.
D.array(D.number).decode([1, 2, 3]) // [1, 2, 3]
D.array(D.number).decode([1, 2, 'not a number']) // nullThe iterable decoder is like the array decoder but accepts any iterable type, instead of just arrays:
D.iterable(D.number).decode(new Set([1, 2, 3])) // [1, 2, 3]
This decoder works the same as D.array except that it parses an object and returns Record<string, D>.
const decoder = D.record(D.number)
const data = {
preschoolers: 55,
student: 124,
employed: 133,
unemployed: 128,
retired: 67
}
decoder.decode(data) // succeeds with data as 'Record<string, number>'
const wrongData = {
preschoolers: null,
student: '124',
employed: 133,
unemployed: 128,
retired: 67
}
decoder.decode(wrongData) // fails because not all of the values are numbersThe key-value pairs decoder works the same way as D.record but returns an array of tuples.
// e.g. with data from previous example
D.keyValuePairs(D.number).forceDecode(data) // succeeds with data as '[[string, number]]'This is probably the most important (and the most complicated?) decoder. You can decode whole typed objects like this:
const person = {
name: 'Sarah',
age: 25
}
const personDecoder = D.object({
required: {
name: D.string,
age: D.number
},
optional: {
preferredName: D.string
}
})
personDecoder.forceDecode(person) // succeedsYou pass it an object which has required and optional object with specified fields. Both required and optional are optional so if you don't have any optional field you can just omit the optional field and vice versa.
Careful,
nullis not a missing value! Null is an actual value which is supposed to be handled withD.nullable(…)
Again, if you want the type of personDecoder, you can use D.Output<…>
type Person = D.Output<typeof personDecoder>
// The above is now equivalent to this interface
interface Person {
name: string
age: number
preferredName?: string
}This one allows you to decode recursive types. However, due to the limitations of TypeScript's type system, we can't have type inference and have to write interfaces to decode to manually.
// We have to define the type manually beforehand
// Let's say that we have a user and they have a first name, last name, and a couple of friends
type User = [string, string, User[]]
// Then, we can create the decoder
const userDecoder = D.tuple(D.string, D.string, D.array(D.recursive(() => userDecoder)))
// This is equivalent
const userDecoder = D.tuple(D.string, D.string, D.recursive(() => D.array(userDecoder)))
// This too is equivalent
const userDecoder = D.recursive(() => D.tuple(D.string, D.string, D.array(userDecoder)))
// And the use it the way you're used to
const bradPitt: User = [
'Brad',
'Pitt',
[
[
'Johnny',
'Depp',
[
['Al', 'Pacino', []]
]
],
['Leonardo', 'DiCaprio', []]
]
]
userDecoder.forceDecode(bradPitt) // succeeds with the recursive type User// Again, you have to define the interface first
interface Category {
name: string,
subcategories: Category[]
}
// And then use `recursive` in the decoder
const categoryDecoder: D.Decoder<Category> = D.object({
required: {
name: D.string,
subcategories: D.array(D.recursive(() => categoryDecoder))
}
})
// This works as well
const categoryDecoder: D.Decoder<Category> = D.recursive(() =>
D.object({
required: {
name: D.string,
subcategories: D.array(categoryDecoder)
}
})
)
const categories = {
name: 'Electronics',
subcategories: [
{
name: 'Computers',
subcategories: [
{ name: 'Desktops', subcategories: [] },
{ name: 'Laptops', subcategories: [] }
]
},
{ name: 'Fridges', subcategories: [] }
]
}
categoryDecoder.forceDecode(categories) // succeedsIf the built-in types in JSON aren't enough for you, you can extend the provided decoders. Let's say you want to decode a Date from an ISO string.
const dateDecoder = D.string.andThen(date => new Date(date))
// You can now use it with
// dateDecoder.decode(…)
// Amazingly, TS is smart enough to allow for this:
type DecodedDate = D.Output<typeof dateDecoder> // is actually Date! and not a stringAlso, if you throw an error from inside the function, the decoder fails as it would fail with a bad type or anything else!
You can use this for:
- Transforming to different types
- Renaming fields in objects
- Performing stricter checks (e.g. string length) and failing the decoder by throwing an error
Now you can decode anything you please—you're unstoppable!
We recommend checking out some of our examples.
io-ts– Schemawax is much much smaller and doesn't require the giganticfp-tslibraryts-auto-guard– Takes the opposite approach and creates decoders from interfaces but requires an extra compilation step and tooling. Hard to use in non-TS projectstypescript-is– Similar tots-auto-guardbut is a transformer for an unofficial version of the TypeScript compiler. Impossible to use without TSyup– Very similar to Schemawax but has some predefined regexes and is 15× larger! Anythingyupcan do should be possible with Schemawaxzod– Again, very similar to Schemawax but better than yup. It is ~10 kB and it is more complex than Schemawax but offers more pre-built functions (but nothing that can't be done with Schemawax).ok-computer– Very simple, only made out of pure functions (which is nice) but there is no type safety or inference