Security News
Input Validation Vulnerabilities Dominate MITRE's 2024 CWE Top 25 List
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
Keep your type definitions in one place, and have but one source of truth for both the runtime validation types and the TypeScript type definitions.
import { DataType } from "dilswer";
export const PersonDataType = DataType.RecordOf({
id: { type: DataType.String, required: true },
name: { type: DataType.String },
age: { type: DataType.Number },
friends: { type: DataType.ArrayOf(DataType.String), required: false },
});
NOTE: the required
attribute in a RecordOf fields is set to true
by
default.
import { GetDataType } from "dilswer";
import { PersonDataType } from "./person-type.ts";
type Person = GetDataType<typeof PersonDataType>;
// Result:
// type Person = {
// friends?: string[];
// id: string;
// name: string;
// age: number;
// }
import { createChecker } from "dilswer";
import { PersonDataType } from "./person-type.ts";
const isPerson = createChecker(PersonDataType);
// Result:
// const isPerson: (data: unknown) => data is {
// friends?: string[];
// id: string;
// name: string;
// age: number;
// }
const person = await axios
.get("https://my-api.io/get-person/1")
.then((r) => r.data);
if (isPerson(person)) {
console.log("Name: ", person.name);
// do something with person
} else {
console.error("`person` variable is not of expected type.");
// handle the validation failure
}
import { createChecker } from "dilswer";
import { PersonDataType } from "./person-type.ts";
const processPerson = createValidatedFunction(
PersonDataType,
(person) => {
console.log("Processing person: ", person.name);
// do something with person
return "Success!";
},
(error) => {
console.error("Function input is not of expected type.");
console.error("Type expected:", error.expectedValueType);
console.error("Received:", error.receivedValue);
console.error("Invalid property location: ", error.fieldPath);
// handle the validation failure
return "Failure";
}
);
// Result:
// const processPerson: (data: unknown) => "Success!" | "Failure"
const person = await axios
.get("https://my-api.io/get-person/1")
.then((r) => r.data);
const result = processPerson(person); // => "Success!" or "Failure"
Whenever you use some kind of a type validation library in a TypeScript project
you will have to define those types twice: once as a TS type
or interface
and once in a format that's understood by the data validation library which will
check the data types on runtime. This is a inconvenience and can sometimes lead
to bugs (when you change one of the definitions but forget to do the same with
the other).
This is the problem that Dilswer is trying to solve. To have one source of truth for your type definitions. One that can be understood by both the TypeScript engine and the data validation library.
Dilswer gives you a tool that you can use to define any kind of type, and then validate data at runtime with against it or infer a TypeScript type directly from it.
will match any string values and translate to the standard string
type in
TypeScript.
will match any number values and translate to the standard number
type in
TypeScript.
will match any true
and false
values and translate to the standard boolean
type in TypeScript.
will match any symbolic values and translate to the symbol
type in TypeScript.
will match only null
value and translate to the standard null
type in
TypeScript.
will match only undefined
value and translate to the standard undefined
type
in TypeScript.
will match any function and translate to the Function
type in TypeScript.
will match any value and translate to the unknown
type in TypeScript.
will match any value matching one of the DataType's provided in the arguments and translate to an TypeScript union type.
Example
const foo = DataType.OneOf(DataType.String, DataType.Number);
type T = GetDataType<typeof foo>; // type T = (string | number)
will match any array which contains only values matching any of the DataType's
provided in the arguments and translate to the Array<...>
type in TypeScript.
Example
const foo = DataType.ArrayOf(DataType.String, DataType.Number);
type T = GetDataType<typeof foo>; // type T = (string | number)[]
will match any object which structure matches the key-value pairs of object properties and FieldDescriptor objects passed to the argument.
Example
const foo = DataType.RecordOf({
bar: { type: DataType.String },
baz: { type: DataType.Number, required: false },
});
type T = GetDataType<typeof foo>; // type T = {bar: string, baz?: number | undefined}
will match any Set object which contains only values matching any of the
DataType's provided in the arguments and translate to the Set<...>
type in
TypeScript.
Example
const foo = DataType.SetOf(DataType.String, DataType.Number);
type T = GetDataType<typeof foo>; // type T = Set<string | number>
will match any value that exactly matches the passed argument and translate to the literal type of that value in TypeScript.
Example's
const foo = DataType.Literal("some-string-literal");
type T0 = GetDataType<typeof foo>; // type T0 = "some-string-literal"
const bar = DataType.Literal(123);
type T1 = GetDataType<typeof bar>; // type T1 = 123
const baz = DataType.Literal(true);
type T2 = GetDataType<typeof baz>; // type T2 = true
will match any value that belongs to an TypeScript enum and translate to that enum type.
enum MyEnum {
A = "A",
B = "B",
}
const foo = DataType.Enum(MyEnum);
type T = GetDataType<typeof foo>; // type T = MyEnum
const validate = createChecker(foo);
validate(MyEnum.A); // => true
will match any value that equals to the specified TypeScript enum member and translate to that enum member type.
enum MyEnum {
A = "VALUE_A",
B = "VALUE_B",
}
const foo = DataType.Enum(MyEnum.A);
type T = GetDataType<typeof foo>; // type T = MyEnum.A
const validate = createChecker(foo);
validate("VALUE_A"); // => true
validate(MyEnum.A); // => true
validate(MyEnum.B); // => false
FAQs
Data validation library with TypeScript integration.
The npm package dilswer receives a total of 82 weekly downloads. As such, dilswer popularity was classified as not popular.
We found that dilswer demonstrated a not healthy version release cadence and project activity because the last version was released 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
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.
Research
Security News
A threat actor's playbook for exploiting the npm ecosystem was exposed on the dark web, detailing how to build a blockchain-powered botnet.