Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/aslilac/succulent
Powerful and easy runtime type checking
https://github.com/aslilac/succulent
typescript
Last synced: 1 day ago
JSON representation
Powerful and easy runtime type checking
- Host: GitHub
- URL: https://github.com/aslilac/succulent
- Owner: aslilac
- License: mit
- Created: 2021-05-20T01:02:28.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2024-08-19T05:01:37.000Z (5 months ago)
- Last Synced: 2024-10-29T22:32:36.973Z (2 months ago)
- Topics: typescript
- Language: TypeScript
- Homepage:
- Size: 634 KB
- Stars: 32
- Watchers: 2
- Forks: 1
- Open Issues: 7
-
Metadata Files:
- Readme: README.md
- Funding: .github/FUNDING.yml
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
README
# Succulent
Powerful and easy runtime type checking
### Motivation
> What if you could just write TypeScript, and get runtime validation for free?
Basically, a lot of equivalent libraries have weird naming and syntax. We already know TypeScript, and that knowledge already does so much for us, but to take the concept a little bit further, and extend our type checking to the runtime, it kind of feels like having to learn another dialect, with all of its subtle differences. Succulent's main goal is to make it feel like you're just writing TypeScript, and for the necessary differences to feel obvious quickly.
Some examples...
- the type `string` is represented by the schema `$string`
- the type `bigint` is represented by the schema `$bigint`
- the type `Date` is represented by the schema `$Date`
- the type `ArrayBuffer` is represented by the schema `$ArrayBuffer`
Getting more complex...
- the type `T[]`/`Array` could be represented by the schema `$Array($T)` _(assuming `$T` is a schema)_
- the type `Map` could be represented by the schema `$Map($K, $V)` _(assuming `$K` and `$V` are schemas)_
- the types `any` and `never` can be represented by the schemas `$any` and `$never` respectively
### Examples
```typescript
import { guard, $string } from "succulent";
/**
* Takes untrusted user input!
*/
export default function (x: unknown): string {
guard(x, $string);
// x now has type `string` and can be treated as such
return x;
}
```
#### More complicated...
```typescript
import {
guard,
hasMaxLength,
matches,
Type,
$Array,
$Date,
$interface,
$optional,
$string,
} from "succulent";
// Use your schema definition to automatically generate TypeScript types.
// Either one of the following should work. The choice is mostly a matter of style.
export type User = Type;
export interface User extends Type {}
// Easily define a reuseable way to validate input from untrusted sources
// By convention, schemas are named after the type they represent, prefixed with `$`.
export const $User = $interface({
id: $string.that(matches(/[A-Za-z0-9_-]{24}/)),
name: $string.that(hasMaxLength(50)),
emailAddresses: $Array($string.that(matches(/[A-Za-z0-9_-]{1,}\@hey\.com/))),
meta: $optional(
$interface({
lastSeen: $optional($Date),
}),
),
});
export default function (user: unknown) {
// You can specify a compatible generic type to use instead of the generated type!
// Mostly helpful for getting nicer editor hints
guard(x, $User);
// x now has type `User`
// ...
}
```
#### Even more complicated...
```typescript
import { guard, inRange, lazy, Schema, $Array, $int, $interface, $string } from "succulent";
type Friend = {
name: string;
happiness: number;
friends: Friend[];
};
// Specifying `Friend` here as a generic ensures that our $Friend schema is
// compatible with the `Friend` type. If they get out of sync, TypeScript will throw
// a compilation error to let you know.
const $Friend: Schema = $interface({
name: $string,
happiness: $int.that(inRange(0, 10)),
// We need to use `lazy` here because $Friend is not yet defined. A little unfortunate,
// but there isn't really a be better way to do this. (unless you know of one, then tell me!)
friends: $Array(lazy(() => $Friend)),
});
export default function (person: unknown) {
try {
guard(person, $Friend);
// person has type `Friend` now!
// ...
} catch (error) {
// Do something with the error, like probe the heirarchy of where errors came from!
}
}
```