biject v2.3.0
biject
Type-safe compile-time bijective maps for TypeScript.
import { biject } from 'biject';
const example = biject<1 | 2, 'a' | 'b'>()(
<const>[
[2, 'a'],
[1, 'b'],
]
);
const foo: 'b' = example.map(1);
const bar: 2 = example.invert('a');
Installation
$ npm install --save biject
$ yarn add biject
To use this package, TypeScript version >= 4.1.0 is required as a peer dependency but using TypeScript >= 4.5 is recommended because it supports mapping sets of bigger sizes through tail-recursion elimination.
If you plan on mapping undefined
or null
values, make sure strictNullChecks
is enabled to avoid them being inferred as any
.
Usage
import { biject } from 'biject';
const example = biject(<const>[
[1, 'one'],
[2, 'two'],
[3, 'three'],
]);
// The map can be used both ways.
example.map(2) // -> 'two'
example.invert('two') // -> 2
Maps that are not bijective will throw compilation errors.
// Fails at compile-time.
biject(<const>[
[1, 'a'],
[1, 'b'],
]);
// Fails at compile-time.
biject(<const>[
[1, 'a'],
[2, 'a'],
]);
The type of query operations is known at compile-time.
const example = biject(<const>[
['kek', 3141],
['lel', 5],
['pip', 927],
]);
// Compiles without error.
const five: 5 = example.map('lel');
const kek: 'kek' = example.invert(3141);
(element: 'kek' | 'pip') => {
const mapsTo: 3141 | 927 = example.map(element);
}
:warning: Correct type inferrence only works if the type of the map given to
biject
exactly represents its run-time value. This is why<const>
is required.
Make sure to not reference any values that TypeScript infers as unions.
:x: Avoid:// Bad. const union = 1 as 1 | 2; biject(<const>[[union, 3]]);
This might lead to run-time errors.
Type-guards
To check if a value is part of the map's domain or codomain (image), there are type-guards available.
// Define the bijection.
const example = biject(<const>[
['a', 1],
['b', 2],
['c', 3],
]);
// Get an unknown value from somewhere.
const element: unknown = document.getElementById('input').value;
if (example.isInDomain(element)) {
// The `element` can now be used in `.map`.
example.map(element);
}
if (example.isInImage(element)) {
// The `element` can now be used in `.invert`.
example.invert(element);
}
Specifying sets
The domain and codomain sets can explicitly be set as unions of elements. This will ensure that the mapping is complete and no elements have been forgotten.
type Domain = 1 | 2 | 3;
type Codomain = 'a' | 'b' | 'c';
// Fails at compile-time.
biject<Domain, Codomain>()(
<const>[
[1, 'c'],
[3, 'a'],
]
);
// Fails at compile-time.
biject<Domain, Codomain>()(
<const>[
[1, 'c'],
[1, 'b'],
[3, 'a'],
]
);
// Compiles without error.
biject<Domain, Codomain>()(
<const>[
[1, 'c'],
[2, 'b'],
[3, 'a'],
]
);
:warning: Note the extra parenthesis in
biject<...>()(...
. This is due to a restriction in TypeScript's type parameter inferrence.