type-mapping

Never trust incoming data. Always check it.

This package was written to help check/sanitize/map data declaratively and comes with batteries included.

Each Mapper is a function.

Goals

• Usability

  It must be easy for developers to understand and use.

  Complex Mappers are created using function composition by default. However, a fluent API also exists and may be used instead.

• Extensibility

  Easy for developers to create their own custom Mappers, and use them with the default ones.

  All Mappers are just functions. Creating a Mapper is as easy as creating a function has certain properties.

• Composability

  Developers should be able to integrate this package into their own packages to boost run-time type safety.

• Use Case Coverage

  The default Mappers should cover 95+% of common data mapping scenarios.

  They should also facilitate building custom Mappers, if they cannot satisfy a custom use case.

  Common use cases,

  • Mapping data from/to incoming HTTP requests/API calls/websocket events
  • Mapping data from/to "schema-on-write" databases (e.g. MySQL)
  • Mapping data from/to "schema-on-read" databases (e.g. Mongo)

• node and Browser support

  This package should work on as many node and Browser environments as possible. This package should have as few run-time dependencies as possible (zero at the moment).

• Safety

  This package must not map data that is invalid. Bugs are inevitable but they should be fixed and tested for as quickly as possible.

Non-Goals

• Performance

  Performance is somewhat a consideration. However, safety, correctness and usability have priority over performance.

• Reflection

Installation

npm install --save type-mapping

Basic Usage

import * as tm from "type-mapping";

const arr = tm.array(tm.stringToUnsignedInteger());
/*
    OK!
    [1,2,3,4,5]
*/
arr("a-name-identifying-this-array", [1,2,3,4,5]);
/*
    OK!
    [1,2,3,4,5]
*/
arr("string-to-unsigned-int", ["1",2,"3",4,5]);
/*
    Error thrown:
    invalid[0] is not an unsigned integer, and cannot be cast
*/
arr("invalid", ["uh-oh",2,"3",4,5]);

const user = tm.object({
    userId : tm.bigInt(),
    firstName : tm.stringLength({ min : 1, max : 1024 }),
    lastName  : tm.stringLength({ min : 1, max : 1024 }),
    banned : tm.boolean(),
});
/*
    OK!
*/
user("john", {
    userId : BigInt(5),
    firstName : "John",
    lastName : "Doe",
    banned : false,
});
/*
    Error thrown:
    invalid.userId must be bigint; received string
*/
user("invalid", {
    userId : "qwerty",
    firstName : "",
    lastName : "Doe",
    banned : 1,
});

const stringOrUndefined = tm.orUndefined(tm.string());
//OK
stringOrUndefined("is-string", "hello");
//OK
stringOrUndefined("is-undefined", undefined);
//Error
stringOrUndefined("is-54", 54);

See the test directory for more examples.

Fluent API

The stringOrUndefined example is simple and shows that you may combine Mappers.

However, with more complex Mappers, function composition gets unwieldly.

A fluent API exists that may be used.

//We changed the import to "type-mapping/fluent"
import * as tm from "type-mapping/fluent";

const stringOrUndefined = tm.string().orUndefined();
//OK
stringOrUndefined("is-string", "hello");
//OK
stringOrUndefined("is-undefined", undefined);
//Error
stringOrUndefined("is-54", 54);

A more complex example,

import * as tm from "type-mapping/fluent";
enum E {
    A = "X",
    B = "Y",
    C = "Z",
}
/*
    Expected Input:
    (
        {
            anEnum: E;
            requiredStringButMayBeUndefined: string | undefined;
            stringOrNumber: string | number;
            nullableMysqlDateTime: Date | null;
            nullableMysqlDateTime2: Date | null;
            arrayOfEnumKey: ("A" | "B" | "C")[];
            literal_1_or_5: 1 | 5;
            nullOrNonEmptyString: string | null;
        } &
        {
            optionalString?: string | undefined;
        }
    )[]

    Output:
    {
        anEnum: E;
        optionalString: string | undefined;
        requiredStringButMayBeUndefined: string | undefined;
        stringOrNumber: string | number;
        nullableMysqlDateTime: Date | null;
        nullableMysqlDateTime2: Date | null;
        arrayOfEnumKey: ("A" | "B" | "C")[];
        literal_1_or_5: 1 | 5;
        nullOrNonEmptyString: string | null;
    }[]
*/
const objArrMapper = tm.object({
    anEnum : tm.enumValue(E),
    optionalString : tm.string().optional(),
    requiredStringButMayBeUndefined : tm.string().orUndefined(),
    stringOrNumber : tm.string().or(tm.finiteNumber()),
    nullableMysqlDateTime : tm.mysql.dateTime().orNull(),
    nullableMysqlDateTime2 : tm.mysql.dateTime(2).orNull(),
    arrayOfEnumKey : tm.enumKey(E).array(),
    literal_1_or_5 : tm.literal(1, 5),
    nullOrNonEmptyString : tm.emptyStringToNull().or(tm.string()),
}).array();

Recommended Usage

As much as possible, use "type-mapping/fluent" and its fluent API.

You should only really need to use type-mapping and its functional API when building custom mappers, or writing a library that utilizes this package for compile-time and run-time type safety.

As much as possible, avoid calling Mappers directly. Use map()/mapMappable() or tryMap()/tryMapMappable() instead.

map() is an alias for mapExpected(). tryMap() is an alias for tryMapExpected().

//Fluent API
import * as tm from "type-mapping/fluent";
//HandledInput  : unknown
//MappableInput : string|number
//ExpectedInput : number
//Output        : number
const strToNum = tm.stringToFiniteNumber();

//== Calling `Mapper` directly ==

//Compile-time: OK
//Run-time    : OK; 1
strToNum("x", "1");
//Compile-time: OK
//Run-time    : OK; 1
strToNum("x", 1);
//Compile-time: OK
//Run-time    : Error; x must be finite number, or finite number string
strToNum("x", "hello");
//Compile-time: OK
//Run-time    : Error; x must be finite number, or finite number string
strToNum("x", true);

//== Calling `map()/mapExpected()` ==

//Compile-time: Error; string not assignable to number
//Run-time    : OK; 1
strToNum.map("x", "1");
//Compile-time: OK
//Run-time    : OK; 1
strToNum.map("x", 1);
//Compile-time: Error; string not assignable to number
//Run-time    : Error; x must be finite number, or finite number string
strToNum.map("x", "hello");
//Compile-time: Error; boolean not assignable to number
//Run-time    : Error; x must be finite number, or finite number string
strToNum.map("x", true);

//== Calling `tryMap()/tryMapExpected()` ==

//Compile-time: Error; string not assignable to number
//Run-time    : { success : true, value : 1 }
strToNum.tryMap("x", "1");
//Compile-time: OK
//Run-time    : { success : true, value : 1 }
strToNum.tryMap("x", 1);
//Compile-time: Error; string not assignable to number
//Run-time    : Error; { success : false, err : Error("x must be finite number, or finite number string") }
strToNum.tryMap("x", "hello");
//Compile-time: Error; boolean not assignable to number
//Run-time    : Error; { success : false, err : Error("x must be finite number, or finite number string") }
strToNum.tryMap("x", true);

//== Calling `mapMappable()` ==

//Compile-time: OK
//Run-time    : OK; 1
strToNum.mapMappable("x", "1");
//Compile-time: OK
//Run-time    : OK; 1
strToNum.mapMappable("x", 1);
//Compile-time: OK
//Run-time    : Error; x must be finite number, or finite number string
strToNum.mapMappable("x", "hello");
//Compile-time: Error; boolean not assignable to string|number
//Run-time    : Error; x must be finite number, or finite number string
strToNum.mapMappable("x", true);

//== Calling `tryMapMappable()` ==

//Compile-time: OK
//Run-time    : { success : true, value : 1 }
strToNum.tryMapMappable("x", "1");
//Compile-time: OK
//Run-time    : { success : true, value : 1 }
strToNum.tryMapMappable("x", 1);
//Compile-time: OK
//Run-time    : Error; { success : false, err : Error("x must be finite number, or finite number string") }
strToNum.tryMapMappable("x", "hello");
//Compile-time: Error; boolean not assignable to string|number
//Run-time    : Error; { success : false, err : Error("x must be finite number, or finite number string") }
strToNum.tryMapMappable("x", true);

With the functional API,

//Functional API
import * as tm from "type-mapping";
//HandledInput  : unknown
//MappableInput : string|number
//ExpectedInput : number
//Output        : number
const strToNum = tm.stringToFiniteNumber();

//Calling `Mapper` directly
//Compile-time: OK
//Run-time    : Error; x must be finite number, or finite number string
strToNum("c", true);

//Calling `map()`
//Compile-time: Error; boolean not assignable to number
//Run-time    : Error; x must be finite number, or finite number string
tm.map(strToNum, "c", true);

//Calling `tryMap()`
//Compile-time: Error; boolean not assignable to number
//Run-time    : Error; { success : false, err : Error("x must be finite number, or finite number string") }
tm.tryMap(strToNum, "c", true);

//Calling `mapMappable()`
//Compile-time: Error; boolean not assignable to string|number
//Run-time    : Error; x must be finite number, or finite number string
tm.mapMappable(strToNum, "c", true);

//Calling `tryMapMappable()`
//Compile-time: Error; boolean not assignable to string|number
//Run-time    : Error; { success : false, err : Error("x must be finite number, or finite number string") }
tm.tryMapMappable(strToNum, "c", true);

When building a package that uses this package for type-safety, try to avoid forcing users to invoke Mappers explicitly.

Instead, have them pass the Mappers to your package, and have your package invoke them behind the scenes.

MappingError

A MappingError is an Error that implements a certain interface.

TODO, more documentation

A MappingError should give you detailed information about why a mapping failed, and should provide enough metadata to let you write a custom error handler.

When created with ErrorUtil.makeMappingError(), all properties of MappingError that are not properties of Error are non-enumerable.

This means that they will not show up if you use Object.keys() or JSON.stringify().

This is intentional because serializing all data about an error may be undesirable, especially if the error contains sensitive information.

You should use ErrorUtil.isMappingError() to detect a MappingError and handle such errors explicitly.

Default Mappers

TODO, document all default mappers

The default mappers may be found in src/functional-lib

MySQL Mappers

TODO, document all default MySQL mappers

The default MySQL mappers may be found in src/mysql-lib

import * as tm from "type-mapping";
const varChar255 = tm.mysql.varChar(255);

Fields

TODO, talk about fields and Name<string>

Decorators

The following decorators are provided,

• @prop(mapper : Mapper)
• @setter(mapper : Mapper)
• @method(...mappers : Mapper[])
• func(...mappers : Mapper[])

func is not quite a decorator but may be used to wrap a function.

@prop

The @prop(mapper : Mapper) decorator is a generic property decorator and takes a single Mapper. This decorator may be used on class properties.

During run-time, the decorator creates a getter and setter on each class instance. Attempts to set the value of the property will pass the value through the Mapper before setting the value.

class Clazz {
    @tm.prop(tm.unsignedInteger().orUndefined())
    x : number|undefined = undefined;
}
const c = new Clazz();
c.x = 1; //OK
c.x = -1; //Error, expected unsigned integer or undefined
c.x = undefined; //OK
c.x = null; //Error, expected unsigned integer or undefined

The @prop decorator also works with class inheritance,

class Base {
    @tm.prop(tm.gt(4))
    prop0 : number = 8;
}
class Derived extends Base {
    @tm.prop(tm.finiteNumber())
    prop0 : number = 9;
}
const c = new Derived();

c.prop0; //9
c.prop0 = 5; //OK
c.prop0 = 4; //Error, expected > 4
c.prop0 = 3; //Error, expected > 4
c.prop0 = 2; //Error, expected > 4
c.prop0 = 1; //Error, expected > 4

@setter

The @setter(mapper : Mapper) decorator is a generic accessor decorator and takes a single Mapper. This decorator may be used on class setters.

During run-time, the decorator replaces the setter on the class prototype. Attempts to set the value of the property will pass the value through the Mapper before being passed to the setter.

let value : number|undefined = undefined;
class Clazz {
    @tm.setter(tm.unsignedInteger().orUndefined())
    set x (v : number|undefined) {
        value = v;
    }
    get x () {
        return value;
    }
}
const c = new Clazz();
c.x = 1; //OK
c.x = -1; //Error, expected unsigned integer or undefined
c.x = undefined; //OK
c.x = null; //Error, expected unsigned integer or undefined

@method

The @method(...mappers : Mapper[]) decorator is a generic method decorator and takes a zero to many Mappers. This decorator may be used on class methods.

During run-time, the decorator replaces the method's value on the class prototype. Attempts to call the method will pass the value through the Mappers before being passed to the method.

let value = 1;
class Clazz {
    @tm.method(tm.finiteNumber())
    foo (v : number) {
        value = v;
    }
}
const c = new Clazz();

c.foo(5);
value; //5
c.foo("6" as any); //Error, expected finite number
value; //5

Rest parameters are also supported, with the following syntax,

let value = 1;
let arr : string[] = [];
class Clazz {
    //Notice the `...[tm.string()]` syntax
    @tm.method(tm.finiteNumber(), ...[tm.string()])
    foo (v : number, ...a : string[]) {
        value = v;
        arr = a;
    }
}
const c = new Clazz();

c.foo(5); //OK
value; //5
arr; //[]

c.foo(6, "a", "b", "c"); //OK
value; //6
arr; //["a", "b", "c"]
c.foo(7, "a", "b", "c", 5 as any); //Error, expected string in argument 4

func

The func(...mappers : Mapper[]) function is not quite a decorator. It is a generic function that takes a zero to many Mappers.

The result may be used to wrap other functions and map their arguments before calling the wrapped functions.

let value = 1;
const foo = tm.func(tm.finiteNumber())(
    (v : number) => {
        value = v;
    }
);

foo(5); //OK
value; //5
foo("6" as any); //Error, expected finite number

Rest parameters are also supported, with the following syntax,

let value = 1;
let arr : string[] = [];
//Notice the `...[tm.string()]` syntax
const foo = tm.func(tm.finiteNumber(), ...[tm.string()])(
    (v : number, ...a : string[]) => {
        value = v;
        arr = a;
    }
)

foo(5); //OK
value; //5
arr; //[]
foo("6" as any); //Error, expected finite number

foo(6, "a", "b", "c"); //OK
value; //6
arr; //["a", "b", "c"]
foo(7, "a", "b", "c", 5 as any); //Error, expected string in argument 4

Custom Mappers

A Mapper is anything that implements the Mapper<> interface,

export interface Mapper<HandledInputT, OutputT> {
    (name : string, mixed : HandledInputT) : OutputT,
}

It is a function with two parameters. name is the name of the value being mapped. mixed is usually a value of type unknown. Extra care is needed to correctly map (or reject) values of type unknown.

Usually, you should implement SafeMapper<>,

export type SafeMapper<OutputT> = (
    Mapper<unknown, OutputT>
);

All Mapper<HandledInputT, OutputT> types must satisfy the following properties,

• Correctness

  When given an input of type HandledInputT, it must handle it correctly.

  It must not silently produce invalid output.

  It must not throw an Error on valid input.

  If you pass an input that is not of type HandledInputT, the behaviour is undefined.

• Idempotence

  A Mapper<> must satisfy the following,

  deepEquals(f(x), f(f(x)))

  That is, if f(0) is "hello", then f("hello") must be "hello".

• Immutability

  A Mapper<> must NEVER modify its input argument.

  That is, all inputs must be treated as immutable.

  A Mapper<> may,

  • Return the same input
  • Return a copy of the input
  • Return a completely different object

An example of a custom mapper,

const evenNumberOnly : tm.SafeMapper<number> = (name : string, mixed : unknown) : number => {
    if (typeof mixed != "number") {
        throw new Error(`${name} must be a number`);
    }
    if (!isFinite(mixed)) {
        throw new Error(`${name} must be a finite number`);
    }
    if (mixed % 2 == 0) {
        return mixed;
    } else {
        throw new Error(`${name} must be an even number`);
    }
};

Now, you may use the mapper as-is, or compose it with other mappers,

import * as tm from "type-mapping";
const evenNumberOrString = tm.or(
    evenNumberOnly,
    tm.string()
);

evenNumberOnly("x", 3); //Error, x must be an even number
evenNumberOnly("x", 4); //OK
evenNumberOnly("x", "qwerty"); //Error, x must be a number

evenNumberOrString("x", 3); //Error, x must be an even number
evenNumberOrString("x", 4); //OK
evenNumberOrString("x", "qwerty"); //OK

Buffer support

TODO, how Buffer is supported on environments that do not support Buffer.

BigInt support

This package supports environments that have bigint primitive support. This package tries its best to support environments that use a BigInt polyfill.

If using a polyfill, the polyfill must satisfy the following,

• Implement function BigInt (value : string|number|bigint) : Object on the global scope (window/global/globalThis).

  It must return an Object. Not a primitive.

• Implement .toString()

The simplest supported polyfill, with no error checking, is,

(global as any).BigInt = ((value : string|number|bigint) => {
    return {
        toString : () => {
            return String(value);
        },
    };
}) as any;

Optional

You may make a mapper optional with optional<>(),

import * as tm from "type-mapping";
const a_or_b = tm.literal("a", "b");
const obj = tm.object({
    x : tm.optional(a_or_b),
});
obj("obj", {});                //OK; { x : undefined }
obj("obj", { x : undefined }); //OK; { x : undefined }
obj("obj", { x : "a" });       //OK; { x : "a" }
obj("obj", { x : "b" });       //OK; { x : "b" }
obj("obj", { x : "c" });       //Error; obj.x must be "a"|"b"

Using optional<>() cancels out runTimeRequired<>()

orUndefined<>()

orUndefined<>() may have surprising behaviour.

Using orUndefined<>() on a field has the following effect,

• The field is required during compile-time
• The field is optional during run-time

This behaviour lets us use the mappers that map undefined to play nicely with JSON serialization.

//Current behaviour
//Compile-time required
//Run-time optional
import * as tm from "type-mapping";
const obj = tm.object({
    x : tm.orUndefined(tm.finiteNumber()),
});
const input = { x : undefined };          //{ x : undefined }
const inputJson = JSON.stringify(input);  //"{}"
const outputJson = JSON.parse(inputJson); //{}
const output = obj("output", outputJson); //{ x : undefined }

vs.

//Technically more "correct" behaviour but harder to use with JSON serialization
//Compile-time required
//Run-time required
import * as tm from "type-mapping";
const obj = tm.object({
    x : tm.orUndefined(tm.finiteNumber()),
});
const input = { x : undefined };          //{ x : undefined }
const inputJson = JSON.stringify(input);  //"{}"
const outputJson = JSON.parse(inputJson); //{}
const output = obj("output", outputJson); //Error; output must have property "x"

To make a field allow undefined but also make the field required,

import * as tm from "type-mapping";
tm.runTimeRequired(tm.orUndefined(myMapper))

Or, with the fluent API,

import * as tm from "type-mapping/fluent";
myMapper.orUndefined().runTimeRequired();

Then, you'll get the following result,

import * as tm from "type-mapping";
const a_or_b = tm.literal("a", "b");
const obj = tm.object({
    x : tm.orUndefined(a_or_b),
});
obj("obj", {});                //OK; { x : undefined }
obj("obj", { x : undefined }); //OK; { x : undefined }
obj("obj", { x : "a" });       //OK; { x : "a" }
obj("obj", { x : "b" });       //OK; { x : "b" }
obj("obj", { x : "c" });       //Error; obj.x must be "a"|"b"

const obj2 = tm.object({
    x : tm.runTimeRequired(tm.orUndefined(a_or_b)),
});
obj("obj2", {});                //Error; obj must have property "x"
obj("obj2", { x : undefined }); //OK; { x : undefined }
obj("obj2", { x : "a" });       //OK; { x : "a" }
obj("obj2", { x : "b" });       //OK; { x : "b" }
obj("obj2", { x : "c" });       //Error; obj2.x must be "a"|"b"

RunTimeRequired

You may make a mapper required during run-time with runTimeRequired<>(),

import * as tm from "type-mapping";
const a_or_b = tm.literal("a", "b");
const obj = tm.object({
    //Required during compile-time
    //Optional during run-time
    x : tm.orUndefined(a_or_b),
});
obj("obj", {});                //OK; { x : undefined }
obj("obj", { x : undefined }); //OK; { x : undefined }
obj("obj", { x : "a" });       //OK; { x : "a" }
obj("obj", { x : "b" });       //OK; { x : "b" }
obj("obj", { x : "c" });       //Error; obj.x must be "a"|"b"

const obj2 = tm.object({
    //Required during compile-time
    //Required during run-time
    x : tm.runTimeRequired(tm.orUndefined(a_or_b)),
});
obj2("obj2", {});                //Error; obj2 must have property "x"
obj2("obj2", { x : undefined }); //OK; { x : undefined }
obj2("obj2", { x : "a" });       //OK; { x : "a" }
obj2("obj2", { x : "b" });       //OK; { x : "b" }
obj2("obj2", { x : "c" });       //Error; obj2.x must be "a"|"b"

Using runTimeRequired<>() cancels out optional<>() but does not remove undefined from the HandledInput/MappableInput/ExpectedInput.

HandledInput vs MappableInput vs ExpectedInput

In general,

• ExpectedInput extends MappableInput
• MappableInput extends HandledInput

The HandledInput of a Mapper is the range of values it will handle correctly.

If given a type inside the range of HandledInput, it must throw an Error on invalid input, and must map valid inputs correctly.

If you pass a type outside the range of HandledInput, the behaviour is undefined.

It may behave as intended, or do something else completely.

The MappableInput of a Mapper is the range of values it will (probably) map successfully.

TypeScript's type system may not be strong enough to fully express the range of values that will map successfully.

But, in an ideal world, passing a type inside the range of MappableInput will always guarantee a successful mapping with zero Errors thrown.

The ExpectedInput of a Mapper is the range of values it would ideally like to receive.

For example, a Mapper may map string values to number, and perform no mapping on number values.

The MappableInput is string|number.

However, in your application logic, you may expect to never pass number to the Mapper.

So, you set the ExpectedInput to string.

import * as tm from "type-mapping";

declare const stringToNumber : (
    & tm.SafeMapper<number>
    & tm.ExpectedInput<string>
    & tm.MappableInput<string|number>
);

//OK
tm.tryMapExpected(stringToNumber, "x", "23");
//Compile-Error, expected string
//Even though this will work during run-time
tm.tryMapExpected(stringToNumber, "x", 23);
//Compile-Error, expected string
//Will also throw an `Error` during run-time
tm.tryMapExpected(stringToNumber, "x", true);

//OK
tm.tryMapMappable(stringToNumber, "x", "23");
//OK, `number` is mappable
tm.tryMapMappable(stringToNumber, "x", 23);
//Compile-Error, expected string|number
//Will also throw an `Error` during run-time
tm.tryMapMappable(stringToNumber, "x", true);

//OK
tm.tryMapHandled(stringToNumber, "x", "23");
//OK
tm.tryMapHandled(stringToNumber, "x", 23);
//OK, HandledInput is `unknown`.
//So, it will handle `boolean` correctly...
//By throwing an `Error` during run-time.
tm.tryMapHandled(stringToNumber, "x", true);

_debug

TODO, how to debug compile-time types

Mapper operations

Mapper predicates

Mapper queries

EnumUtil

BigIntUtil

ErrorUtil

TypeUtil

Contributing

Tests

npm run sanity-check

The above command rebuilds this package and runs the compile-time and run-time tests.

Compatibility with schema-decorator

This package is the successor to schema-decorator, and meant to replace it. Many breaking changes have been made.

In particular, the concept of Accepts and CanAccept have been replaced with, ExpectedInput and MappableInput respectively.

There is no Field class anymore. Instead, a Mapper is a Field when it also extends the Name<> interface.

Apart from those breaking changes, you may use the mappers here with the mappers from schema-decorator.

The route declaration feature has also been removed and has been split into,

• https://github.com/anyhowstep/route-declaration
• https://github.com/anyhowstep/route-client

Other packages using typed-orm

• https://github.com/anyhowstep/route-declaration

  route-declaration is used to declare HTTP routes

• https://github.com/anyhowstep/route-client

  Uses route-declaration to provide compile-time and run-time type-safe API calls.

  Uses axios to send requests by default. May be extended to use other request senders.

• https://github.com/anyhowstep/route-express

  Uses route-declaration to provide compile-time and run-time type-safe API servers.

  Is a thin wrapper over express.

  Provides compile-time type-safe res.locals manipulation.

• https://github.com/anyhowstep/typed-orm

  Experimental MySQL 5.7 query builder and ORM.

  Wraps https://github.com/mysqljs/mysql and provides compile-time and run-time type-safe SQL expression composition, and query building.

  Supports connection pooling and transactions.

• https://github.com/AnyhowStep/tsql

  Work-in-progress rewrite of typed-orm.

  Improved version of the experimental typed-orm.

  Intended to act as a database-agnostic base package to support multiple databases. (PostgreSQL, MariaDB, SQLite3, MySQL, etc.)

• https://github.com/anyhowstep/tsql-mysql-5.7

  Work-in-progress rewrite of typed-orm.

  Uses tsql to implement MySQL 5.7-specific operators, functions, and syntax.

Cookbook

The examples here use the fluent API.

(TODO, examples of common data mapping scenarios and how to handle them)

Breaking Changes

• 1.3.0 -> 1.4.0

  • optional() still makes a field compile-time optional.
  • optional() still makes a field run-time optional.
  • orUndefined() now makes a field run-time optional. Use runTimeRequired() to make it run-time required again. This breaking change was introduced to make usage with JSON serialization easier.
  • runTimeRequired() added
  • runTimeRequired() makes a field compile-time required.
  • runTimeRequired() makes a field run-time required.

• 1.20.0 -> 1.21.0

  • mysql.decimal() now returns the Decimal interface and not string. This breaking change was introduced because not much code should break and this increases type safety overall.

• 1.24.0 -> 1.25.0

  • mysql.xxxIntXxx() functions now return bigint and not number. This breaking change was introduced because this increases type safety overall. This also follows the general direction the tsql project wants to follow.