Security News
Maven Central Adds Sigstore Signature Validation
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.
@standard-schema/utils
Advanced tools
There are two common tasks that third-party libraries perform after validation fails. The first is to flatten the issues by creating a dot path to more easily associate the issues with the input data. This is commonly used in form libraries. The second is to throw an error that contains all the issue information. To simplify both tasks, Standard Schema also ships a utils package that provides a getDotPath
function and a SchemaError
class.
npm install @standard-schema/utils # npm
yarn add @standard-schema/utils # yarn
pnpm add @standard-schema/utils # pnpm
bun add @standard-schema/utils # bun
deno add jsr:@standard-schema/utils # deno
To generate a dot path, simply pass an issue to the getDotPath
function. If the issue does not contain a path or the path contains a key that is not of type string
or number
, the function returns null
.
import type { v1 } from "@standard-schema/spec";
import { getDotPath } from "@standard-schema/utils";
async function getFormErrors(schema: v1.StandardSchema, data: unknown) {
const result = await schema["~standard"].validate({ value: data });
const formErrors: string[] = [];
const fieldErrors: Record<string, string[]> = {};
if (result.issues) {
for (const issue of result.issues) {
const dotPath = getDotPath(issue);
if (dotPath) {
if (fieldErrors[dotPath]) {
fieldErrors[dotPath].push(issue.message);
} else {
fieldErrors[dotPath] = [issue.message];
}
} else {
formErrors.push(issue.message);
}
}
}
return { formErrors, fieldErrors };
}
To throw an error that contains all issue information, simply pass the issues of the failed schema validation to the SchemaError
class. The SchemaError
class extends the Error
class with an issues
property that contains all the issues.
import type { v1 } from "@standard-schema/spec";
import { SchemaError } from "@standard-schema/utils";
async function validateInput<TSchema extends v1.StandardSchema>(
schema: TSchema,
data: unknown,
): Promise<v1.InferOutput<TSchema>> {
const result = await schema["~standard"].validate({ value: data });
if (result.issues) {
throw new SchemaError(result.issues);
}
return result.value;
}
FAQs
The official runtime utils for Standard Schema
The npm package @standard-schema/utils receives a total of 0 weekly downloads. As such, @standard-schema/utils popularity was classified as not popular.
We found that @standard-schema/utils demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers 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
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.
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.