@maroonedog/luq 2.2.0 → 2.3.1

package/dist/standard-schema/emit-field-schema.js

@@ -0,0 +1,68 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.emitFieldSchema = emitFieldSchema;
+const plugin_keyword_map_1 = require("./plugin-keyword-map");
+const unrepresentable_rule_error_1 = require("./unrepresentable-rule-error");
+/** Slot to JSON Schema type name; undefined when it cannot be decided. */
+const TYPE_OF_SLOT = Object.freeze({
+    string: "string",
+    number: "number",
+    boolean: "boolean",
+    array: "array",
+    object: "object",
+    // date is not a JSON type. Draft-07 convention writes it as a string with
+    // `format: "date-time"`, but the date slot judges Date instances, which
+    // are not JSON values. Counted as unwritable rather than conflated.
+});
+function typeOf(calls) {
+    const slots = new Set(calls.map((call) => call.slot));
+    slots.delete("any");
+    if (slots.size !== 1)
+        return undefined;
+    const [slot] = [...slots];
+    return slot === undefined ? undefined : TYPE_OF_SLOT[slot];
+}
+/**
+ * How `type` is spelled. Draft-07 expresses `.nullable()` as a list of
+ * types (`{"type": ["string", "null"]}`). `{"nullable": true}` is the
+ * OpenAPI 3.0 spelling and is not in the JSON Schema vocabulary.
+ */
+function typeKeyword(calls, fieldPath, policy) {
+    const isInteger = calls.some((call) => call.pluginName === "numberInteger");
+    const isNullable = calls.some((call) => call.pluginName === "nullable");
+    const base = isInteger ? "integer" : typeOf(calls);
+    if (base === undefined) {
+        if (policy === "throw") {
+            throw new unrepresentable_rule_error_1.UnrepresentableRuleError(fieldPath, "the chain", "its declarations do not settle on one JSON type");
+        }
+        return {};
+    }
+    return { type: isNullable ? [base, "null"] : base };
+}
+/** Makes one field's schema from that field's declared calls. */
+function emitFieldSchema(fieldPath, calls, policy) {
+    if (calls.length === 0 && policy === "throw") {
+        throw new unrepresentable_rule_error_1.UnrepresentableRuleError(fieldPath, "this field", "no declaration was recorded for it (it was not built through the " +
+            "builder chain)");
+    }
+    const schema = typeKeyword(calls, fieldPath, policy);
+    for (const call of calls) {
+        const toKeywords = plugin_keyword_map_1.PLUGIN_KEYWORDS[call.pluginName];
+        if (toKeywords === undefined) {
+            if (policy === "throw") {
+                throw new unrepresentable_rule_error_1.UnrepresentableRuleError(fieldPath, call.pluginName, "no JSON Schema keyword expresses it");
+            }
+            continue;
+        }
+        const keywords = toKeywords(call.args);
+        if (keywords === null)
+            continue;
+        Object.assign(schema, keywords);
+    }
+    return {
+        schema,
+        // `.optional()` counts wherever it appears in the chain, not only first.
+        isRequired: calls.some((call) => call.pluginName === "required") &&
+            !calls.some((call) => call.pluginName === "optional"),
+    };
+}

package/dist/standard-schema/emit-field-schema.mjs

@@ -0,0 +1,65 @@
+import { PLUGIN_KEYWORDS } from "./plugin-keyword-map.mjs";
+import { UnrepresentableRuleError, } from "./unrepresentable-rule-error.mjs";
+/** Slot to JSON Schema type name; undefined when it cannot be decided. */
+const TYPE_OF_SLOT = Object.freeze({
+    string: "string",
+    number: "number",
+    boolean: "boolean",
+    array: "array",
+    object: "object",
+    // date is not a JSON type. Draft-07 convention writes it as a string with
+    // `format: "date-time"`, but the date slot judges Date instances, which
+    // are not JSON values. Counted as unwritable rather than conflated.
+});
+function typeOf(calls) {
+    const slots = new Set(calls.map((call) => call.slot));
+    slots.delete("any");
+    if (slots.size !== 1)
+        return undefined;
+    const [slot] = [...slots];
+    return slot === undefined ? undefined : TYPE_OF_SLOT[slot];
+}
+/**
+ * How `type` is spelled. Draft-07 expresses `.nullable()` as a list of
+ * types (`{"type": ["string", "null"]}`). `{"nullable": true}` is the
+ * OpenAPI 3.0 spelling and is not in the JSON Schema vocabulary.
+ */
+function typeKeyword(calls, fieldPath, policy) {
+    const isInteger = calls.some((call) => call.pluginName === "numberInteger");
+    const isNullable = calls.some((call) => call.pluginName === "nullable");
+    const base = isInteger ? "integer" : typeOf(calls);
+    if (base === undefined) {
+        if (policy === "throw") {
+            throw new UnrepresentableRuleError(fieldPath, "the chain", "its declarations do not settle on one JSON type");
+        }
+        return {};
+    }
+    return { type: isNullable ? [base, "null"] : base };
+}
+/** Makes one field's schema from that field's declared calls. */
+export function emitFieldSchema(fieldPath, calls, policy) {
+    if (calls.length === 0 && policy === "throw") {
+        throw new UnrepresentableRuleError(fieldPath, "this field", "no declaration was recorded for it (it was not built through the " +
+            "builder chain)");
+    }
+    const schema = typeKeyword(calls, fieldPath, policy);
+    for (const call of calls) {
+        const toKeywords = PLUGIN_KEYWORDS[call.pluginName];
+        if (toKeywords === undefined) {
+            if (policy === "throw") {
+                throw new UnrepresentableRuleError(fieldPath, call.pluginName, "no JSON Schema keyword expresses it");
+            }
+            continue;
+        }
+        const keywords = toKeywords(call.args);
+        if (keywords === null)
+            continue;
+        Object.assign(schema, keywords);
+    }
+    return {
+        schema,
+        // `.optional()` counts wherever it appears in the chain, not only first.
+        isRequired: calls.some((call) => call.pluginName === "required") &&
+            !calls.some((call) => call.pluginName === "optional"),
+    };
+}

package/dist/standard-schema/index.d.ts

@@ -4,3 +4,8 @@ export type { IssuePathSegments } from "./split-issue-path";
 export { splitIssuePath } from "./split-issue-path";
 export type { StandardLuqSchema } from "./to-standard-schema";
 export { toStandardSchema } from "./to-standard-schema";
+export type { JsonSchemaOptions, StandardJsonSchemaLuqSchema, } from "./to-standard-json-schema";
+export { toStandardJsonSchema } from "./to-standard-json-schema";
+export { DeclarationsUnavailableError } from "./declarations-unavailable-error";
+export { UnsupportedJsonSchemaTargetError } from "./json-schema-target";
+export { UnrepresentableRuleError, type UnrepresentablePolicy, } from "./unrepresentable-rule-error";

package/dist/standard-schema/index.js

@@ -1,7 +1,15 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.toStandardSchema = exports.splitIssuePath = void 0;
+exports.UnrepresentableRuleError = exports.UnsupportedJsonSchemaTargetError = exports.DeclarationsUnavailableError = exports.toStandardJsonSchema = exports.toStandardSchema = exports.splitIssuePath = void 0;
 var split_issue_path_1 = require("./split-issue-path");
 Object.defineProperty(exports, "splitIssuePath", { enumerable: true, get: function () { return split_issue_path_1.splitIssuePath; } });
 var to_standard_schema_1 = require("./to-standard-schema");
 Object.defineProperty(exports, "toStandardSchema", { enumerable: true, get: function () { return to_standard_schema_1.toStandardSchema; } });
+var to_standard_json_schema_1 = require("./to-standard-json-schema");
+Object.defineProperty(exports, "toStandardJsonSchema", { enumerable: true, get: function () { return to_standard_json_schema_1.toStandardJsonSchema; } });
+var declarations_unavailable_error_1 = require("./declarations-unavailable-error");
+Object.defineProperty(exports, "DeclarationsUnavailableError", { enumerable: true, get: function () { return declarations_unavailable_error_1.DeclarationsUnavailableError; } });
+var json_schema_target_1 = require("./json-schema-target");
+Object.defineProperty(exports, "UnsupportedJsonSchemaTargetError", { enumerable: true, get: function () { return json_schema_target_1.UnsupportedJsonSchemaTargetError; } });
+var unrepresentable_rule_error_1 = require("./unrepresentable-rule-error");
+Object.defineProperty(exports, "UnrepresentableRuleError", { enumerable: true, get: function () { return unrepresentable_rule_error_1.UnrepresentableRuleError; } });

package/dist/standard-schema/index.mjs

@@ -1,2 +1,6 @@
 export { splitIssuePath } from "./split-issue-path.mjs";
 export { toStandardSchema } from "./to-standard-schema.mjs";
+export { toStandardJsonSchema } from "./to-standard-json-schema.mjs";
+export { DeclarationsUnavailableError } from "./declarations-unavailable-error.mjs";
+export { UnsupportedJsonSchemaTargetError } from "./json-schema-target.mjs";
+export { UnrepresentableRuleError, } from "./unrepresentable-rule-error.mjs";

package/dist/standard-schema/json-schema-target.d.ts

@@ -0,0 +1,6 @@
+export declare class UnsupportedJsonSchemaTargetError extends Error {
+    readonly target: string;
+    constructor(target: string);
+}
+/** Returns the `$schema` for a supported target; throws for anything else. */
+export declare function resolveJsonSchemaTarget(target: string): string;

package/dist/standard-schema/json-schema-target.js

@@ -0,0 +1,44 @@
+"use strict";
+// ===========================================================================
+// L10 src/standard-schema/json-schema-target.ts
+//
+// Takes the spec's `target` and admits only what is actually supported.
+//
+// The spec says to throw on an unsupported target, and it is right to: writing
+// draft-07 silently when 2020-12 was asked for hands the caller a document
+// they will read under the wrong rules.
+//
+// Two are supported, draft-2020-12 and draft-07 — the two the spec names as
+// widely used and strongly recommends implementing. openapi-3.0 descends from
+// draft-04 and is a different lineage, so it is not admitted on a guess.
+//
+// Across the vocabulary currently emitted, the two differ only in `$schema`:
+// every keyword written today is spelled and means the same in both. Tuples
+// would differ, and are not emitted. This is where the branch goes if that
+// changes.
+// ===========================================================================
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.UnsupportedJsonSchemaTargetError = void 0;
+exports.resolveJsonSchemaTarget = resolveJsonSchemaTarget;
+/** The supported targets, and the `$schema` each one announces. */
+const SCHEMA_URI = Object.freeze({
+    "draft-2020-12": "https://json-schema.org/draft/2020-12/schema",
+    "draft-07": "http://json-schema.org/draft-07/schema#",
+});
+class UnsupportedJsonSchemaTargetError extends Error {
+    constructor(target) {
+        super(`Luq does not emit JSON Schema for the target "${target}". ` +
+            `Supported targets: ${Object.keys(SCHEMA_URI).join(", ")}.`);
+        this.target = target;
+        this.name = "UnsupportedJsonSchemaTargetError";
+    }
+}
+exports.UnsupportedJsonSchemaTargetError = UnsupportedJsonSchemaTargetError;
+/** Returns the `$schema` for a supported target; throws for anything else. */
+function resolveJsonSchemaTarget(target) {
+    const schemaUri = SCHEMA_URI[target];
+    if (schemaUri === undefined) {
+        throw new UnsupportedJsonSchemaTargetError(target);
+    }
+    return schemaUri;
+}

package/dist/standard-schema/json-schema-target.mjs

@@ -0,0 +1,39 @@
+// ===========================================================================
+// L10 src/standard-schema/json-schema-target.ts
+//
+// Takes the spec's `target` and admits only what is actually supported.
+//
+// The spec says to throw on an unsupported target, and it is right to: writing
+// draft-07 silently when 2020-12 was asked for hands the caller a document
+// they will read under the wrong rules.
+//
+// Two are supported, draft-2020-12 and draft-07 — the two the spec names as
+// widely used and strongly recommends implementing. openapi-3.0 descends from
+// draft-04 and is a different lineage, so it is not admitted on a guess.
+//
+// Across the vocabulary currently emitted, the two differ only in `$schema`:
+// every keyword written today is spelled and means the same in both. Tuples
+// would differ, and are not emitted. This is where the branch goes if that
+// changes.
+// ===========================================================================
+/** The supported targets, and the `$schema` each one announces. */
+const SCHEMA_URI = Object.freeze({
+    "draft-2020-12": "https://json-schema.org/draft/2020-12/schema",
+    "draft-07": "http://json-schema.org/draft-07/schema#",
+});
+export class UnsupportedJsonSchemaTargetError extends Error {
+    constructor(target) {
+        super(`Luq does not emit JSON Schema for the target "${target}". ` +
+            `Supported targets: ${Object.keys(SCHEMA_URI).join(", ")}.`);
+        this.target = target;
+        this.name = "UnsupportedJsonSchemaTargetError";
+    }
+}
+/** Returns the `$schema` for a supported target; throws for anything else. */
+export function resolveJsonSchemaTarget(target) {
+    const schemaUri = SCHEMA_URI[target];
+    if (schemaUri === undefined) {
+        throw new UnsupportedJsonSchemaTargetError(target);
+    }
+    return schemaUri;
+}

package/dist/standard-schema/plugin-keyword-map.d.ts

@@ -0,0 +1,3 @@
+/** A keyword fragment made from the arguments; null means type or presence handles it. */
+export type ToKeywords = (args: readonly unknown[]) => Record<string, unknown> | null;
+export declare const PLUGIN_KEYWORDS: Readonly<Record<string, ToKeywords>>;

package/dist/standard-schema/plugin-keyword-map.js

@@ -0,0 +1,93 @@
+"use strict";
+// ===========================================================================
+// L10 src/standard-schema/plugin-keyword-map.ts
+//
+// "This plugin, called with these arguments, means this JSON Schema keyword."
+// The reading direction of keyword-map-*.ts, reusing the correspondence those
+// files already settled rather than inventing a second one.
+//
+// Plugin names are written as STRINGS. Importing the plugins themselves would
+// drag every one of them into the bundle of anyone who emits a schema, which
+// does not fit "you only ship what you used". A test cross-checks each string
+// against the real `plugin.name`, so the names cannot drift without the cost.
+//
+// A plugin that is not listed here cannot be written out. A plugin the user
+// wrote themselves is never listed, so it never can. That is a consequence of
+// the design rather than an oversight, and it surfaces as
+// UnrepresentableRuleError instead of being hidden.
+// ===========================================================================
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.PLUGIN_KEYWORDS = void 0;
+const numberAt = (args, index) => typeof args[index] === "number" ? args[index] : Number.NaN;
+/**
+ * A second argument makes `.min(n)` exclusive. The same boundary the
+ * reading direction draws when it maps `exclusiveMinimum`.
+ */
+const boundOf = (inclusive, exclusive) => (args) => ({
+    [args[1] === true ? exclusive : inclusive]: numberAt(args, 0),
+});
+/** A format with no arguments: the name is the `format` value verbatim. */
+const format = (name) => () => ({ format: name });
+exports.PLUGIN_KEYWORDS = Object.freeze({
+    // --- strings ----------------------------------------------------------
+    stringMin: (args) => ({ minLength: numberAt(args, 0) }),
+    stringMax: (args) => ({ maxLength: numberAt(args, 0) }),
+    stringExactLength: (args) => ({
+        minLength: numberAt(args, 0),
+        maxLength: numberAt(args, 0),
+    }),
+    // Draft-07's `pattern` is an ECMA-262 SOURCE string. Flags cannot be
+    // spelled there, and dropping them changes the meaning, so a flagged
+    // RegExp counts as unwritable rather than being silently narrowed.
+    stringPattern: (args) => args[0] instanceof RegExp ? { pattern: args[0].source } : null,
+    stringContentEncoding: (args) => ({ contentEncoding: args[0] }),
+    stringContentMediaType: (args) => ({ contentMediaType: args[0] }),
+    // --- formats (names taken verbatim from the format map) ---------------
+    stringDatetime: format("date-time"),
+    stringDate: format("date"),
+    stringTime: format("time"),
+    stringDuration: format("duration"),
+    stringEmail: format("email"),
+    stringIdnEmail: format("idn-email"),
+    stringHostname: format("hostname"),
+    stringIdnHostname: format("idn-hostname"),
+    stringIpv4: format("ipv4"),
+    stringIpv6: format("ipv6"),
+    // `url` is not a registered JSON Schema format name. Both spellings map
+    // to this plugin on the reading side, but a writer has to pick one, so it
+    // picks the registered `uri`.
+    stringUrl: format("uri"),
+    stringUriReference: format("uri-reference"),
+    stringIri: format("iri"),
+    stringIriReference: format("iri-reference"),
+    stringUriTemplate: format("uri-template"),
+    stringJsonPointer: format("json-pointer"),
+    stringRelativeJsonPointer: format("relative-json-pointer"),
+    stringRegex: format("regex"),
+    uuid: format("uuid"),
+    // --- numbers ----------------------------------------------------------
+    numberMin: boundOf("minimum", "exclusiveMinimum"),
+    numberMax: boundOf("maximum", "exclusiveMaximum"),
+    numberMultipleOf: (args) => ({ multipleOf: numberAt(args, 0) }),
+    numberRange: (args) => ({
+        minimum: numberAt(args, 0),
+        maximum: numberAt(args, 1),
+    }),
+    numberPositive: () => ({ exclusiveMinimum: 0 }),
+    numberNegative: () => ({ exclusiveMaximum: 0 }),
+    // --- arrays -----------------------------------------------------------
+    arrayMinLength: (args) => ({ minItems: numberAt(args, 0) }),
+    arrayMaxLength: (args) => ({ maxItems: numberAt(args, 0) }),
+    arrayUnique: () => ({ uniqueItems: true }),
+    // --- values -----------------------------------------------------------
+    literal: (args) => ({ const: args[0] }),
+    oneOf: (args) => (Array.isArray(args[0]) ? { enum: args[0] } : null),
+    // --- handled by type or presence, adding no keyword -------------------
+    // numberInteger becomes `type: "integer"`, so it feeds the type decision.
+    numberInteger: () => null,
+    required: () => null,
+    optional: () => null,
+    nullable: () => null,
+    // Changes the order things run in, not the set of accepted values.
+    skip: () => null,
+});

package/dist/standard-schema/plugin-keyword-map.mjs

@@ -0,0 +1,90 @@
+// ===========================================================================
+// L10 src/standard-schema/plugin-keyword-map.ts
+//
+// "This plugin, called with these arguments, means this JSON Schema keyword."
+// The reading direction of keyword-map-*.ts, reusing the correspondence those
+// files already settled rather than inventing a second one.
+//
+// Plugin names are written as STRINGS. Importing the plugins themselves would
+// drag every one of them into the bundle of anyone who emits a schema, which
+// does not fit "you only ship what you used". A test cross-checks each string
+// against the real `plugin.name`, so the names cannot drift without the cost.
+//
+// A plugin that is not listed here cannot be written out. A plugin the user
+// wrote themselves is never listed, so it never can. That is a consequence of
+// the design rather than an oversight, and it surfaces as
+// UnrepresentableRuleError instead of being hidden.
+// ===========================================================================
+const numberAt = (args, index) => typeof args[index] === "number" ? args[index] : Number.NaN;
+/**
+ * A second argument makes `.min(n)` exclusive. The same boundary the
+ * reading direction draws when it maps `exclusiveMinimum`.
+ */
+const boundOf = (inclusive, exclusive) => (args) => ({
+    [args[1] === true ? exclusive : inclusive]: numberAt(args, 0),
+});
+/** A format with no arguments: the name is the `format` value verbatim. */
+const format = (name) => () => ({ format: name });
+export const PLUGIN_KEYWORDS = Object.freeze({
+    // --- strings ----------------------------------------------------------
+    stringMin: (args) => ({ minLength: numberAt(args, 0) }),
+    stringMax: (args) => ({ maxLength: numberAt(args, 0) }),
+    stringExactLength: (args) => ({
+        minLength: numberAt(args, 0),
+        maxLength: numberAt(args, 0),
+    }),
+    // Draft-07's `pattern` is an ECMA-262 SOURCE string. Flags cannot be
+    // spelled there, and dropping them changes the meaning, so a flagged
+    // RegExp counts as unwritable rather than being silently narrowed.
+    stringPattern: (args) => args[0] instanceof RegExp ? { pattern: args[0].source } : null,
+    stringContentEncoding: (args) => ({ contentEncoding: args[0] }),
+    stringContentMediaType: (args) => ({ contentMediaType: args[0] }),
+    // --- formats (names taken verbatim from the format map) ---------------
+    stringDatetime: format("date-time"),
+    stringDate: format("date"),
+    stringTime: format("time"),
+    stringDuration: format("duration"),
+    stringEmail: format("email"),
+    stringIdnEmail: format("idn-email"),
+    stringHostname: format("hostname"),
+    stringIdnHostname: format("idn-hostname"),
+    stringIpv4: format("ipv4"),
+    stringIpv6: format("ipv6"),
+    // `url` is not a registered JSON Schema format name. Both spellings map
+    // to this plugin on the reading side, but a writer has to pick one, so it
+    // picks the registered `uri`.
+    stringUrl: format("uri"),
+    stringUriReference: format("uri-reference"),
+    stringIri: format("iri"),
+    stringIriReference: format("iri-reference"),
+    stringUriTemplate: format("uri-template"),
+    stringJsonPointer: format("json-pointer"),
+    stringRelativeJsonPointer: format("relative-json-pointer"),
+    stringRegex: format("regex"),
+    uuid: format("uuid"),
+    // --- numbers ----------------------------------------------------------
+    numberMin: boundOf("minimum", "exclusiveMinimum"),
+    numberMax: boundOf("maximum", "exclusiveMaximum"),
+    numberMultipleOf: (args) => ({ multipleOf: numberAt(args, 0) }),
+    numberRange: (args) => ({
+        minimum: numberAt(args, 0),
+        maximum: numberAt(args, 1),
+    }),
+    numberPositive: () => ({ exclusiveMinimum: 0 }),
+    numberNegative: () => ({ exclusiveMaximum: 0 }),
+    // --- arrays -----------------------------------------------------------
+    arrayMinLength: (args) => ({ minItems: numberAt(args, 0) }),
+    arrayMaxLength: (args) => ({ maxItems: numberAt(args, 0) }),
+    arrayUnique: () => ({ uniqueItems: true }),
+    // --- values -----------------------------------------------------------
+    literal: (args) => ({ const: args[0] }),
+    oneOf: (args) => (Array.isArray(args[0]) ? { enum: args[0] } : null),
+    // --- handled by type or presence, adding no keyword -------------------
+    // numberInteger becomes `type: "integer"`, so it feeds the type decision.
+    numberInteger: () => null,
+    required: () => null,
+    optional: () => null,
+    nullable: () => null,
+    // Changes the order things run in, not the set of accepted values.
+    skip: () => null,
+});

package/dist/standard-schema/split-issue-path.d.ts

@@ -1,9 +1,11 @@
-/** 開いた結果。オブジェクトのキーは string、配列の添字は number。 */
+/** The opened path: object keys as strings, array indices as numbers. */
 export type IssuePathSegments = readonly (string | number)[];
 /**
- * ルート ("") は空配列。空配列は仕様上「ルート自身への issue」を意味する。
+ * The root ("") is the empty list, which the spec reads as an issue on the
+ * root itself.
  *
- * 解釈できない形が来たら、握り潰さずに path 全体を1つの文字列セグメントとして
- * 返す。issue を落とすより、開けなかったことが分かる形で渡すほうがまし。
+ * A shape that cannot be interpreted comes back as the whole path in one
+ * string segment rather than being swallowed. Handing over something visibly
+ * unopened beats dropping the issue.
  */
 export declare function splitIssuePath(path: string): IssuePathSegments;

package/dist/standard-schema/split-issue-path.js

@@ -2,26 +2,28 @@
 // ===========================================================================
 // L10 src/standard-schema/split-issue-path.ts
 //
-// Luq の issue path ("items[1].productId") を Standard Schema の path
-// (["items", 1, "productId"]) に開く。
+// Opens an issue path ("items[1].productId") into the spec's segment list
+// (["items", 1, "productId"]).
 //
-// 方向に注意: これは formatIssuePath の逆で、宣言パス (parseFieldPath が
-// 読む "items[*].productId") のパーサではない。issue path には [*] が
-// 決して現れず、代わりに実インデックスが入る。二つの文法を一つの関数で
-// 扱おうとすると、[*] を 0 と読むような取り違えが静かに入るので分けてある。
+// Mind the direction: this reverses issue-path FORMATTING, and is not a parser
+// for declared paths. An issue path never contains [*] — it carries the real
+// index instead. Handling both grammars in one function is how [*] quietly
+// starts being read as 0, so they are kept apart.
 //
-// 配列インデックスは number として出す。仕様の PropertyKey は
-// string | number | symbol を許し、消費側 (フォームライブラリ) は
-// 添字を number として受け取る前提で書かれているため。
+// Array indices come out as numbers. The spec's PropertyKey allows
+// string | number | symbol, and the consumers — form libraries — are written
+// expecting a number.
 // ===========================================================================
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.splitIssuePath = splitIssuePath;
 const INDEX_PATTERN = /^\[(\d+)\]/;
 /**
- * ルート ("") は空配列。空配列は仕様上「ルート自身への issue」を意味する。
+ * The root ("") is the empty list, which the spec reads as an issue on the
+ * root itself.
  *
- * 解釈できない形が来たら、握り潰さずに path 全体を1つの文字列セグメントとして
- * 返す。issue を落とすより、開けなかったことが分かる形で渡すほうがまし。
+ * A shape that cannot be interpreted comes back as the whole path in one
+ * string segment rather than being swallowed. Handing over something visibly
+ * unopened beats dropping the issue.
  */
 function splitIssuePath(path) {
     if (path === "")
@@ -54,7 +56,7 @@ function splitIssuePath(path) {
     }
     return expectKey ? [path] : segments;
 }
-/** キーは "." か "[" の手前まで。どちらも無ければ末尾まで。 */
+/** A key runs to the next "." or "[", or to the end when there is neither. */
 function findKeyEnd(rest) {
     const dot = rest.indexOf(".");
     const bracket = rest.indexOf("[");

package/dist/standard-schema/split-issue-path.mjs

@@ -1,24 +1,26 @@
 // ===========================================================================
 // L10 src/standard-schema/split-issue-path.ts
 //
-// Luq の issue path ("items[1].productId") を Standard Schema の path
-// (["items", 1, "productId"]) に開く。
+// Opens an issue path ("items[1].productId") into the spec's segment list
+// (["items", 1, "productId"]).
 //
-// 方向に注意: これは formatIssuePath の逆で、宣言パス (parseFieldPath が
-// 読む "items[*].productId") のパーサではない。issue path には [*] が
-// 決して現れず、代わりに実インデックスが入る。二つの文法を一つの関数で
-// 扱おうとすると、[*] を 0 と読むような取り違えが静かに入るので分けてある。
+// Mind the direction: this reverses issue-path FORMATTING, and is not a parser
+// for declared paths. An issue path never contains [*] — it carries the real
+// index instead. Handling both grammars in one function is how [*] quietly
+// starts being read as 0, so they are kept apart.
 //
-// 配列インデックスは number として出す。仕様の PropertyKey は
-// string | number | symbol を許し、消費側 (フォームライブラリ) は
-// 添字を number として受け取る前提で書かれているため。
+// Array indices come out as numbers. The spec's PropertyKey allows
+// string | number | symbol, and the consumers — form libraries — are written
+// expecting a number.
 // ===========================================================================
 const INDEX_PATTERN = /^\[(\d+)\]/;
 /**
- * ルート ("") は空配列。空配列は仕様上「ルート自身への issue」を意味する。
+ * The root ("") is the empty list, which the spec reads as an issue on the
+ * root itself.
  *
- * 解釈できない形が来たら、握り潰さずに path 全体を1つの文字列セグメントとして
- * 返す。issue を落とすより、開けなかったことが分かる形で渡すほうがまし。
+ * A shape that cannot be interpreted comes back as the whole path in one
+ * string segment rather than being swallowed. Handing over something visibly
+ * unopened beats dropping the issue.
  */
 export function splitIssuePath(path) {
     if (path === "")
@@ -51,7 +53,7 @@ export function splitIssuePath(path) {
     }
     return expectKey ? [path] : segments;
 }
-/** キーは "." か "[" の手前まで。どちらも無ければ末尾まで。 */
+/** A key runs to the next "." or "[", or to the end when there is neither. */
 function findKeyEnd(rest) {
     const dot = rest.indexOf(".");
     const bracket = rest.indexOf("[");

package/dist/standard-schema/standard-schema.types.d.ts

@@ -1,4 +1,4 @@
-/** 仕様の StandardSchemaV1。Input と Output を型として運ぶ。 */
+/** The spec's StandardSchemaV1, carrying Input and Output as types. */
 export interface StandardSchemaV1<Input = unknown, Output = Input> {
     readonly "~standard": StandardSchemaProps<Input, Output>;
 }
@@ -7,8 +7,8 @@ export interface StandardSchemaProps<Input = unknown, Output = Input> {
     readonly vendor: string;
     readonly validate: (value: unknown, options?: StandardSchemaOptions | undefined) => StandardSchemaResult<Output> | Promise<StandardSchemaResult<Output>>;
     /**
-     * 実行時には存在しない。型を運ぶためだけのメンバーで、仕様がそう定めている。
-     * InferInput / InferOutput はここから読む。
+     * Absent at run time. The spec defines it as a type-only member, and it is
+     * what InferInput / InferOutput read.
      */
     readonly types?: StandardSchemaTypes<Input, Output> | undefined;
 }
@@ -25,8 +25,9 @@ export interface StandardSchemaFailure {
     readonly issues: readonly StandardSchemaIssue[];
 }
 /**
- * path は仕様上 optional。Luq は必ず入れる (root への issue は空配列)。
- * 省略と「ルートを指す」を呼び出し側が区別できるようにするため。
+ * The spec makes path optional; it is always present here, with an issue on
+ * the root carrying the empty list. That keeps "omitted" distinguishable from
+ * "points at the root" on the consuming side.
  */
 export interface StandardSchemaIssue {
     readonly message: string;
@@ -38,8 +39,8 @@ export interface StandardSchemaPathSegment {
 export type InferStandardInput<Schema extends StandardSchemaV1> = NonNullable<Schema["~standard"]["types"]>["input"];
 export type InferStandardOutput<Schema extends StandardSchemaV1> = NonNullable<Schema["~standard"]["types"]>["output"];
 /**
- * validate の第2引数。仕様が定めているので受ける。
- * libraryOptions はベンダーごとの追加パラメータで、Luq はまだ何も定義していない。
+ * validate's second parameter, declared because the spec defines it.
+ * libraryOptions is the per-vendor extension point, and none is defined yet.
  */
 export interface StandardSchemaOptions {
     readonly libraryOptions?: Record<string, unknown> | undefined;

package/dist/standard-schema/standard-schema.types.js

@@ -2,12 +2,12 @@
 // ===========================================================================
 // L10 src/standard-schema/standard-schema.types.ts
 //
-// Standard Schema v1 の型を自前で宣言する。@standard-schema/spec に依存しない。
-// 仕様が「型だけのパッケージなので inline してよい」と明示しており、依存を
-// 足せば利用者の node_modules に1つ増える一方で、得るものは何も無いため。
-// 形が仕様からずれていないことは test/type/standard-schema/ が固定する。
+// Declares the Standard Schema v1 types here rather than depending on the
+// spec package. The spec explicitly permits inlining, being types only, and a
+// dependency would add an entry to every user's node_modules for nothing.
+// Type tests pin the shape against the spec so it cannot drift.
 //
-// この層が L10 なのは、Validator (L6) の上に載る変換であり、コアの誰も
-// これを import しないから。import の向きは L6 -> L10 ではなく L10 -> L6。
+// This is the outermost layer because it is a view laid over the validator and
+// nothing in the core imports it. The import direction runs inwards only.
 // ===========================================================================
 Object.defineProperty(exports, "__esModule", { value: true });