Security News
38% of CISOs Fear They’re Not Moving Fast Enough on AI
CISOs are racing to adopt AI for cybersecurity, but hurdles in budgets and governance may leave some falling behind in the fight against cyber threats.
generic-type-guard
Advanced tools
Source: https://github.com/mscharley/generic-type-guard
Author: Matthew Scharley
Contributors: See contributors on GitHub
Bugs/Support: Github Issues
Copyright: 2017
License: MIT license
Status: Active
This library is an attempt to manage creating type guards in a sensible way, making them composable and reusable.
$ npm i generic-type-guard
The point of this library is to provide a suite of type guard expressions that are themselves both type safe and composable in a type safe way. To that end we define two new types which are just aliases for the built-in type guard type:
export type PartialTypeGuard<T, U extends T> = (value: T) => value is U;
export type TypeGuard<T> = PartialTypeGuard<unknown, T>;
A PartialTypeGuard
is a type guard which given a value of type T
can prove it is
actually the specialised type U
. A TypeGuard
is a type guard that can prove any value
to be of type T
; it is a PartialTypeGuard<unknown, T>
.
What do we mean by type safety when we're talking about something that in a lot of ways is inherantly type unsafe? We simply mean that if you change the definition your interface/variable/whatever you are checking then your type guard should no longer successfully compile. Most of the type safety comes from leveraging the compiler, therefore you must define your typeguards in the following way to make them the most effective:
interface Foo {
foo: string;
bar: number;
}
// this fails.
const isBrokenFoo: tg.TypeGuard<Foo> =
tg.isRecord("foo", tg.isString);
// this works.
const isFoo: tg.TypeGuard<Foo> =
new tg.IsInterface().withProperty("foo", tg.isString).withProperty("bar", tg.isNumber).get();
// This works around the gotchas explained below but has other issues, especially with complex types.
// All guarantees are void if you use this format.
const isFoo =
new tg.IsInterface().withProperty("foo", tg.isString).withProperty("bar", tg.isNumber).get();
It is highly recommended to assign an explicit type to the type guards you create to let the compiler ensure that you've caught everything.
Some examples:
import * as tg from "generic-type-guard";
export interface TestInterface {
str: string;
num: number;
}
const isTypeSafeTestInterface: tg.PartialTypeGuard<{}, TestInterface> =
tg.isIntersection(tg.hasProperty("str", tg.isString), tg.hasProperty("num", tg.isNumber));
export const isTestInterface: TypeGuard<TestInterface> = (o: any): o is TestInterface =>
isObject(o) && isTypeSafeTestInterface(o);
// or perhaps you have a larger interface...
export interface ComplexInterface extends TestInterface {
b: boolean;
maybeString?: string;
nullableString: string | null;
}
export const isTypeSafeComplexInterface: tg.TypeGuard<ComplexInterface> =
new tg.IsInterface()
.withProperty("str", tg.isString)
.withProperty("num", tg.isNumber)
.withProperty("b", tg.isBoolean)
.withProperty("maybeString", tg.isOptional(tg.isString))
.withProperty("nullableString", tg.isNullable(tg.isString))
.get();
// Alternatively:
export const isTypeSafeComplexInterface2: tg.PartialTypeGuard<{}, ComplexInterface> =
new tg.IntersectionOf(tg.hasProperty("str", tg.isString))
.with(tg.hasProperty("num", tg.isNumber))
.with(tg.hasProperty("b", tg.isBoolean))
.with(tg.hasProperty("maybeString", tg.isUnion(tg.isUndefined, tg.isString)))
.with(tg.hasProperty("nullableString", tg.isNullable(tg.isString))).get();
There are more detailed examples available.
generic-type-guard
works with the TypeScript type system. You are guaranteed that the type guards you write are sufficient to prove
that the thing provided to it conforms in one way or another to the type that the type guard checks for. But that doesn't necessarily mean
that all valid values of that type will be allowed. Put another way, you are guaranteed to never get a false positive but you may get false
negatives. In particular, union types can be troublesome.
An example helps illustrate this:
import * as tg from "generic-type-guard";
type FooBar = "foo" | "bar";
const isFooBar: tg.TypeGuard<FooBar> = tg.isSingletonString("foo");
The above example checks for a single value "foo"
. This is a FooBar and so the type system does not complain. But if you try to pass
"bar"
into this type guard then it will return false.
Perhaps more insidiously:
interface Foo {
foo?: string;
}
const isFoo: tg.TypeGuard<Foo> = tg.isRecord("foo", tg.isString);
Again, checking that foo
is a string is sufficient to prove that it is either a string or undefined.
FAQs
Generic type guards for TypeScript
The npm package generic-type-guard receives a total of 1,882 weekly downloads. As such, generic-type-guard popularity was classified as popular.
We found that generic-type-guard demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
CISOs are racing to adopt AI for cybersecurity, but hurdles in budgets and governance may leave some falling behind in the fight against cyber threats.
Research
Security News
Socket researchers uncovered a backdoored typosquat of BoltDB in the Go ecosystem, exploiting Go Module Proxy caching to persist undetected for years.
Security News
Company News
Socket is joining TC54 to help develop standards for software supply chain security, contributing to the evolution of SBOMs, CycloneDX, and Package URL specifications.