@nestia/core 14.0.0 → 14.0.2

package/lib/options/IRequestHeadersValidator.d.ts

@@ -1,16 +1,83 @@
 import { IValidation } from "typia";
 export type IRequestHeadersValidator<T> = IRequestHeadersValidator.IAssert<T> | IRequestHeadersValidator.IIs<T> | IRequestHeadersValidator.IValidate<T>;
+/**
+ * The request headers validator that the transform passes to `TypedHeaders`.
+ *
+ * The literal `type` field selects which typia function generated the
+ * validator: `assert`, `is`, or `validate`. `validate_request_headers` turns a
+ * failure of any variant into a 400 response.
+ *
+ * @evidence contracts/common.md#principled-implementation The union is discriminated by the literal `type`, so the runtime selects the assert, is, or validate path with one comparison and the compiler checks that each variant carries the function its tag names.
+ * @evidence contracts/common.md#clear-and-simple-design Three variants, one per typia function family, with no shared base because each function has a different shape.
+ * @evidence contracts/common.md#prohibited-implementation-shortcuts It is a type and adds no runtime behavior; the runtime rejects an unknown `type` with an error instead of accepting it.
+ * @evidence contracts/common.md#meaningful-documentation The comment names the decorators that receive the validator, the meaning of the discriminant, and the response a failure becomes.
+ * @evidenceExclude contracts/portability.md#os-neutral-implementation The validator consumes HTTP header records and returns decoded values independently of native filesystem or process spelling.
+ */
 export declare namespace IRequestHeadersValidator {
+    /**
+     * Validator generated from `typia.assert`.
+     *
+     * @evidence contracts/common.md#principled-implementation The variant tags a function of the header record of the request, whose values are strings, string arrays, or undefined that returns the decoded object or throws the `TypeGuardError` of typia; `validate_request_headers` catches the error and converts it to a `BadRequestException` carrying the path, reason, expected type, and value of the first failure.
+     * @evidence contracts/common.md#clear-and-simple-design A two-member record, the tag and the function.
+     * @evidence contracts/common.md#prohibited-implementation-shortcuts It is a type and adds no runtime behavior.
+     * @evidence contracts/common.md#meaningful-documentation The comment names the typia function the variant comes from; the failure response is stated on the union.
+     * @evidenceExclude contracts/portability.md#os-neutral-implementation The validator consumes HTTP header records and returns decoded values independently of native filesystem or process spelling.
+     */
     interface IAssert<T> {
         type: "assert";
+        /**
+         * The typia assertion function generated for the requested type.
+         *
+         * @evidence contracts/common.md#principled-implementation The transform generates the function for the type argument of the decorator, taking the header record of the request, whose values are strings, string arrays, or undefined and it returns the decoded object or throws the `TypeGuardError` of typia.
+         * @evidence contracts/common.md#clear-and-simple-design One function member with the input the decorator has.
+         * @evidence contracts/common.md#prohibited-implementation-shortcuts The function is generated from the type, and the runtime never edits its result.
+         * @evidence contracts/common.md#meaningful-documentation The comment states that the function is generated for the requested type; its input is in the signature.
+         * @evidenceExclude contracts/portability.md#os-neutral-implementation The validator consumes HTTP header records and returns decoded values independently of native filesystem or process spelling.
+         */
         assert: (input: Record<string, string | string[] | undefined>) => T;
     }
+    /**
+     * Validator generated from `typia.is`.
+     *
+     * @evidence contracts/common.md#principled-implementation The variant tags a function of the header record of the request, whose values are strings, string arrays, or undefined that returns the decoded object or `null`; a failing result becomes a `BadRequestException` with only the fixed message, because `typia.is` records no failure detail.
+     * @evidence contracts/common.md#clear-and-simple-design A two-member record, the tag and the function.
+     * @evidence contracts/common.md#prohibited-implementation-shortcuts It is a type and adds no runtime behavior.
+     * @evidence contracts/common.md#meaningful-documentation The comment names the typia function the variant comes from.
+     * @evidenceExclude contracts/portability.md#os-neutral-implementation The validator consumes HTTP header records and returns decoded values independently of native filesystem or process spelling.
+     */
     interface IIs<T> {
         type: "is";
+        /**
+         * The typia check function generated for the requested type.
+         *
+         * @evidence contracts/common.md#principled-implementation The transform generates the function for the type argument of the decorator, taking the header record of the request, whose values are strings, string arrays, or undefined and returning the decoded object or `null`.
+         * @evidence contracts/common.md#clear-and-simple-design One function member with the input the decorator has.
+         * @evidence contracts/common.md#prohibited-implementation-shortcuts The function is generated from the type, and the runtime never edits its result.
+         * @evidence contracts/common.md#meaningful-documentation The comment states that the function is generated for the requested type; its result is in the signature.
+         * @evidenceExclude contracts/portability.md#os-neutral-implementation The validator consumes HTTP header records and returns decoded values independently of native filesystem or process spelling.
+         */
         is: (input: Record<string, string | string[] | undefined>) => T | null;
     }
+    /**
+     * Validator generated from `typia.validate`.
+     *
+     * @evidence contracts/common.md#principled-implementation The variant tags a function of the header record of the request, whose values are strings, string arrays, or undefined that returns the `IValidation` of typia; a failed result becomes a `BadRequestException` carrying every error of the validation.
+     * @evidence contracts/common.md#clear-and-simple-design A two-member record, the tag and the function.
+     * @evidence contracts/common.md#prohibited-implementation-shortcuts It is a type and adds no runtime behavior.
+     * @evidence contracts/common.md#meaningful-documentation The comment names the typia function the variant comes from.
+     * @evidenceExclude contracts/portability.md#os-neutral-implementation The validator consumes HTTP header records and returns decoded values independently of native filesystem or process spelling.
+     */
     interface IValidate<T> {
         type: "validate";
+        /**
+         * The typia validation function generated for the requested type.
+         *
+         * @evidence contracts/common.md#principled-implementation The transform generates the function for the type argument of the decorator, taking the header record of the request, whose values are strings, string arrays, or undefined and returning the validation result with every error.
+         * @evidence contracts/common.md#clear-and-simple-design One function member with the input the decorator has.
+         * @evidence contracts/common.md#prohibited-implementation-shortcuts The function is generated from the type, and the runtime never edits its result.
+         * @evidence contracts/common.md#meaningful-documentation The comment states that the function is generated for the requested type; its result is in the signature.
+         * @evidenceExclude contracts/portability.md#os-neutral-implementation The validator consumes HTTP header records and returns decoded values independently of native filesystem or process spelling.
+         */
         validate: (input: Record<string, string | string[] | undefined>) => IValidation<T>;
     }
 }

package/lib/options/IRequestQueryValidator.d.ts

@@ -1,16 +1,84 @@
 import { IValidation } from "typia";
 export type IRequestQueryValidator<T> = IRequestQueryValidator.IAssert<T> | IRequestQueryValidator.IIs<T> | IRequestQueryValidator.IValidate<T>;
+/**
+ * The request query validator that the transform passes to `TypedQuery`,
+ * `TypedQuery.Body`, and `WebSocketRoute.Query`.
+ *
+ * The literal `type` field selects which typia function generated the
+ * validator: `assert`, `is`, or `validate`. `validate_request_query` turns a
+ * failure of any variant into a 400 response.
+ *
+ * @evidence contracts/common.md#principled-implementation The union is discriminated by the literal `type`, so the runtime selects the assert, is, or validate path with one comparison and the compiler checks that each variant carries the function its tag names.
+ * @evidence contracts/common.md#clear-and-simple-design Three variants, one per typia function family, with no shared base because each function has a different shape.
+ * @evidence contracts/common.md#prohibited-implementation-shortcuts It is a type and adds no runtime behavior; the runtime rejects an unknown `type` with an error instead of accepting it.
+ * @evidence contracts/common.md#meaningful-documentation The comment names the decorators that receive the validator, the meaning of the discriminant, and the response a failure becomes.
+ * @evidenceExclude contracts/portability.md#os-neutral-implementation The validator consumes URLSearchParams and describes query data rather than native paths or process arguments.
+ */
 export declare namespace IRequestQueryValidator {
+    /**
+     * Validator generated from `typia.assert`.
+     *
+     * @evidence contracts/common.md#principled-implementation The variant tags a function of the `URLSearchParams` of the query string or of an urlencoded body that returns the decoded object or throws the `TypeGuardError` of typia; `validate_request_query` catches the error and converts it to a `BadRequestException` carrying the path, reason, expected type, and value of the first failure, and a message-only one when a required property is missing.
+     * @evidence contracts/common.md#clear-and-simple-design A two-member record, the tag and the function.
+     * @evidence contracts/common.md#prohibited-implementation-shortcuts It is a type and adds no runtime behavior.
+     * @evidence contracts/common.md#meaningful-documentation The comment names the typia function the variant comes from; the failure response is stated on the union.
+     * @evidenceExclude contracts/portability.md#os-neutral-implementation The validator consumes URLSearchParams and describes query data rather than native paths or process arguments.
+     */
     interface IAssert<T> {
         type: "assert";
+        /**
+         * The typia assertion function generated for the requested type.
+         *
+         * @evidence contracts/common.md#principled-implementation The transform generates the function for the type argument of the decorator, taking the `URLSearchParams` of the query string or of an urlencoded body and it returns the decoded object or throws the `TypeGuardError` of typia.
+         * @evidence contracts/common.md#clear-and-simple-design One function member with the input the decorator has.
+         * @evidence contracts/common.md#prohibited-implementation-shortcuts The function is generated from the type, and the runtime never edits its result.
+         * @evidence contracts/common.md#meaningful-documentation The comment states that the function is generated for the requested type; its input is in the signature.
+         * @evidenceExclude contracts/portability.md#os-neutral-implementation The validator consumes URLSearchParams and describes query data rather than native paths or process arguments.
+         */
         assert: (input: URLSearchParams) => T;
     }
+    /**
+     * Validator generated from `typia.is`.
+     *
+     * @evidence contracts/common.md#principled-implementation The variant tags a function of the `URLSearchParams` of the query string or of an urlencoded body that returns the decoded object or `null`; a failing result becomes a `BadRequestException` with only the fixed message, because `typia.is` records no failure detail.
+     * @evidence contracts/common.md#clear-and-simple-design A two-member record, the tag and the function.
+     * @evidence contracts/common.md#prohibited-implementation-shortcuts It is a type and adds no runtime behavior.
+     * @evidence contracts/common.md#meaningful-documentation The comment names the typia function the variant comes from.
+     * @evidenceExclude contracts/portability.md#os-neutral-implementation The validator consumes URLSearchParams and describes query data rather than native paths or process arguments.
+     */
     interface IIs<T> {
         type: "is";
+        /**
+         * The typia check function generated for the requested type.
+         *
+         * @evidence contracts/common.md#principled-implementation The transform generates the function for the type argument of the decorator, taking the `URLSearchParams` of the query string or of an urlencoded body and returning the decoded object or `null`.
+         * @evidence contracts/common.md#clear-and-simple-design One function member with the input the decorator has.
+         * @evidence contracts/common.md#prohibited-implementation-shortcuts The function is generated from the type, and the runtime never edits its result.
+         * @evidence contracts/common.md#meaningful-documentation The comment states that the function is generated for the requested type; its result is in the signature.
+         * @evidenceExclude contracts/portability.md#os-neutral-implementation The validator consumes URLSearchParams and describes query data rather than native paths or process arguments.
+         */
         is: (input: URLSearchParams) => T | null;
     }
+    /**
+     * Validator generated from `typia.validate`.
+     *
+     * @evidence contracts/common.md#principled-implementation The variant tags a function of the `URLSearchParams` of the query string or of an urlencoded body that returns the `IValidation` of typia; a failed result becomes a `BadRequestException` carrying every error of the validation.
+     * @evidence contracts/common.md#clear-and-simple-design A two-member record, the tag and the function.
+     * @evidence contracts/common.md#prohibited-implementation-shortcuts It is a type and adds no runtime behavior.
+     * @evidence contracts/common.md#meaningful-documentation The comment names the typia function the variant comes from.
+     * @evidenceExclude contracts/portability.md#os-neutral-implementation The validator consumes URLSearchParams and describes query data rather than native paths or process arguments.
+     */
     interface IValidate<T> {
         type: "validate";
+        /**
+         * The typia validation function generated for the requested type.
+         *
+         * @evidence contracts/common.md#principled-implementation The transform generates the function for the type argument of the decorator, taking the `URLSearchParams` of the query string or of an urlencoded body and returning the validation result with every error.
+         * @evidence contracts/common.md#clear-and-simple-design One function member with the input the decorator has.
+         * @evidence contracts/common.md#prohibited-implementation-shortcuts The function is generated from the type, and the runtime never edits its result.
+         * @evidence contracts/common.md#meaningful-documentation The comment states that the function is generated for the requested type; its result is in the signature.
+         * @evidenceExclude contracts/portability.md#os-neutral-implementation The validator consumes URLSearchParams and describes query data rather than native paths or process arguments.
+         */
         validate: (input: URLSearchParams) => IValidation<T>;
     }
 }

package/lib/options/IResponseBodyQuerifier.d.ts

@@ -1,20 +1,144 @@
 import { IValidation } from "typia";
-export type IResponseBodyQuerifier<T> = IResponseBodyquerifier.IStringify<T> | IResponseBodyquerifier.IIs<T> | IResponseBodyquerifier.IAssert<T> | IResponseBodyquerifier.IValidate<T>;
+/**
+ * The serializer that the transform passes to `TypedQuery.Get`,
+ * `TypedQuery.Post`, `TypedQuery.Put`, `TypedQuery.Patch`, and
+ * `TypedQuery.Delete` for the urlencoded form of the response body.
+ *
+ * The literal `type` field selects which generated encoder/validator
+ * combination it contains: `stringify` (no validation), `is`, `assert`,
+ * `validate`, or `validate.log`. `get_path_and_querify` turns a failing
+ * validation into a 500 response, except `validate.log`, which logs the failure
+ * and answers with the plain conversion of the data into `URLSearchParams`.
+ *
+ * @evidence contracts/common.md#principled-implementation The union is discriminated by the literal `type`, so the runtime selects the serializer with one comparison; the transform combines its URLSearchParams encoder with assert, is or validate checks as selected, while stringify performs encoding alone and validate.log reports failures before fallback encoding.
+ * @evidence contracts/common.md#clear-and-simple-design Five variants describe plain encoding and the three validation callback shapes, with validate.log sharing the validate shape but selecting a different failure policy.
+ * @evidence contracts/common.md#prohibited-implementation-shortcuts It is a type and adds no runtime behavior; the runtime rejects an unknown `type` with an error instead of accepting it.
+ * @evidence contracts/common.md#meaningful-documentation The comment names the decorators that receive the serializer and the response each variant produces on a failed validation.
+ * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe conversion of JavaScript response values to HTTP query text without native file access.
+ */
+export type IResponseBodyQuerifier<T> = IResponseBodyquerifier.IStringify<T> | IResponseBodyquerifier.IIs<T> | IResponseBodyquerifier.IAssert<T> | IResponseBodyquerifier.IValidate<T> | IResponseBodyquerifier.IValidateLog<T>;
+/**
+ * The variant records of {@link IResponseBodyQuerifier}.
+ *
+ * The lowercase q is the spelling of the exported namespace name, which
+ * existing code may reference.
+ *
+ * @evidence contracts/common.md#principled-implementation The namespace declares the five variant records that IResponseBodyQuerifier combines, so the union and its variants are one public family.
+ * @evidence contracts/common.md#clear-and-simple-design Five records with no runtime members.
+ * @evidence contracts/common.md#prohibited-implementation-shortcuts It contains types only; the spelling is kept because renaming an exported identifier is a breaking change.
+ * @evidence contracts/common.md#meaningful-documentation The comment states what the namespace holds and why its name has a lowercase q.
+ * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe conversion of JavaScript response values to HTTP query text without native file access.
+ */
 export declare namespace IResponseBodyquerifier {
+    /**
+     * Generated URLSearchParams encoder without validation.
+     *
+     * @evidence contracts/common.md#principled-implementation The variant tags a function that serializes the data as it is, so a value of the wrong type is serialized as far as its shape allows without this variant performing validation.
+     * @evidence contracts/common.md#clear-and-simple-design A two-member record, the tag and the function.
+     * @evidence contracts/common.md#prohibited-implementation-shortcuts It is a type and adds no runtime behavior.
+     * @evidence contracts/common.md#meaningful-documentation The comment identifies how validation and URLSearchParams encoding are combined.
+     * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe conversion of JavaScript response values to HTTP query text without native file access.
+     */
     interface IStringify<T> {
         type: "stringify";
+        /**
+         * The generated function of the variant, taking the response data.
+         *
+         * @evidence contracts/common.md#principled-implementation The transform generates the function for the return type of the route method, and the runtime uses the result as the response body as it is.
+         * @evidence contracts/common.md#clear-and-simple-design One function member.
+         * @evidence contracts/common.md#prohibited-implementation-shortcuts The function is generated from the type, and the runtime never edits its result.
+         * @evidence contracts/common.md#meaningful-documentation The comment states that the function is generated for the return type; its result is in the signature.
+         * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe conversion of JavaScript response values to HTTP query text without native file access.
+         */
         stringify: (input: T) => URLSearchParams;
     }
+    /**
+     * Generated URLSearchParams encoder guarded by a typia is check.
+     *
+     * @evidence contracts/common.md#principled-implementation The variant tags a function that returns the encoded URLSearchParams, or `null` when the data is not of the type; `null` becomes a 500 `InternalServerErrorException` with a fixed message.
+     * @evidence contracts/common.md#clear-and-simple-design A two-member record, the tag and the function.
+     * @evidence contracts/common.md#prohibited-implementation-shortcuts It is a type and adds no runtime behavior.
+     * @evidence contracts/common.md#meaningful-documentation The comment identifies how validation and URLSearchParams encoding are combined.
+     * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe conversion of JavaScript response values to HTTP query text without native file access.
+     */
     interface IIs<T> {
         type: "is";
+        /**
+         * The generated function of the variant, taking the response data.
+         *
+         * @evidence contracts/common.md#principled-implementation The transform generates the function for the return type of the route method, and it returns the serialized text or `null`.
+         * @evidence contracts/common.md#clear-and-simple-design One function member.
+         * @evidence contracts/common.md#prohibited-implementation-shortcuts The function is generated from the type, and the runtime never edits its result.
+         * @evidence contracts/common.md#meaningful-documentation The comment states that the function is generated for the return type; its result is in the signature.
+         * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe conversion of JavaScript response values to HTTP query text without native file access.
+         */
         is: (input: T) => URLSearchParams | null;
     }
+    /**
+     * Generated URLSearchParams encoder preceded by a typia assertion.
+     *
+     * @evidence contracts/common.md#principled-implementation The variant tags a function that returns the serialized text or throws the `TypeGuardError` of typia, which becomes a 500 `InternalServerErrorException` with the path, reason, expected type, and value.
+     * @evidence contracts/common.md#clear-and-simple-design A two-member record, the tag and the function.
+     * @evidence contracts/common.md#prohibited-implementation-shortcuts It is a type and adds no runtime behavior.
+     * @evidence contracts/common.md#meaningful-documentation The comment identifies how validation and URLSearchParams encoding are combined.
+     * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe conversion of JavaScript response values to HTTP query text without native file access.
+     */
     interface IAssert<T> {
         type: "assert";
+        /**
+         * The generated function of the variant, taking the response data.
+         *
+         * @evidence contracts/common.md#principled-implementation The transform generates the function for the return type of the route method, and it returns the encoded URLSearchParams or throws.
+         * @evidence contracts/common.md#clear-and-simple-design One function member.
+         * @evidence contracts/common.md#prohibited-implementation-shortcuts The function is generated from the type, and the runtime never edits its result.
+         * @evidence contracts/common.md#meaningful-documentation The comment states that the function is generated for the return type; its result is in the signature.
+         * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe conversion of JavaScript response values to HTTP query text without native file access.
+         */
         assert: (input: T) => URLSearchParams;
     }
+    /**
+     * Generated URLSearchParams encoder wrapped in a typia validation result.
+     *
+     * @evidence contracts/common.md#principled-implementation The variant tags a function that returns IValidation<URLSearchParams>; a failure becomes a 500 `InternalServerErrorException` carrying every error.
+     * @evidence contracts/common.md#clear-and-simple-design A two-member record, the tag and the function.
+     * @evidence contracts/common.md#prohibited-implementation-shortcuts It is a type and adds no runtime behavior.
+     * @evidence contracts/common.md#meaningful-documentation The comment identifies how validation and URLSearchParams encoding are combined.
+     * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe conversion of JavaScript response values to HTTP query text without native file access.
+     */
     interface IValidate<T> {
         type: "validate";
+        /**
+         * The generated function of the variant, taking the response data.
+         *
+         * @evidence contracts/common.md#principled-implementation The transform generates the function for the return type of the route method, and it returns the validation result.
+         * @evidence contracts/common.md#clear-and-simple-design One function member.
+         * @evidence contracts/common.md#prohibited-implementation-shortcuts The function is generated from the type, and the runtime never edits its result.
+         * @evidence contracts/common.md#meaningful-documentation The comment states that the function is generated for the return type; its result is in the signature.
+         * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe conversion of JavaScript response values to HTTP query text without native file access.
+         */
+        validate: (input: T) => IValidation<URLSearchParams>;
+    }
+    /**
+     * Generated validation and URLSearchParams encoding for the `validate.log`
+     * mode.
+     *
+     * @evidence contracts/common.md#principled-implementation The variant tags the same function shape as `validate`, but a failure is passed to the logger registered with `TypedRoute.setValidateErrorLogger` and the response is the plain conversion of the data into `URLSearchParams`, so a validation failure never changes the status.
+     * @evidence contracts/common.md#clear-and-simple-design A two-member record, the tag and the function.
+     * @evidence contracts/common.md#prohibited-implementation-shortcuts It is a type and adds no runtime behavior.
+     * @evidence contracts/common.md#meaningful-documentation The comment identifies how validation and URLSearchParams encoding are combined.
+     * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe conversion of JavaScript response values to HTTP query text without native file access.
+     */
+    interface IValidateLog<T> {
+        type: "validate.log";
+        /**
+         * The generated function of the variant, taking the response data.
+         *
+         * @evidence contracts/common.md#principled-implementation The transform generates the function for the return type of the route method, and it returns the validation result.
+         * @evidence contracts/common.md#clear-and-simple-design One function member.
+         * @evidence contracts/common.md#prohibited-implementation-shortcuts The function is generated from the type, and the runtime never edits its result.
+         * @evidence contracts/common.md#meaningful-documentation The comment states that the function is generated for the return type; its result is in the signature.
+         * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe conversion of JavaScript response values to HTTP query text without native file access.
+         */
         validate: (input: T) => IValidation<URLSearchParams>;
     }
 }

package/lib/options/IResponseBodyStringifier.d.ts

@@ -1,24 +1,131 @@
 import { IValidation } from "typia";
 export type IResponseBodyStringifier<T> = IResponseBodyStringifier.IStringify<T> | IResponseBodyStringifier.IIs<T> | IResponseBodyStringifier.IAssert<T> | IResponseBodyStringifier.IValidate<T> | IResponseBodyStringifier.IValidateLog<T>;
+/**
+ * The serializer that the transform passes to `TypedRoute` and `EncryptedRoute`
+ * for the JSON text of the response body.
+ *
+ * The literal `type` field selects which typia function generated it:
+ * `stringify` (no validation), `is`, `assert`, `validate`, or `validate.log`.
+ * `get_path_and_stringify` turns a failing validation into a 500 response,
+ * except `validate.log`, which logs the failure and answers with
+ * `JSON.stringify` of the data.
+ *
+ * @evidence contracts/common.md#principled-implementation The union is discriminated by the literal `type`, so the runtime selects the serializer with one comparison; the five variants are the typia stringify families, of which four validate the data and one does not.
+ * @evidence contracts/common.md#clear-and-simple-design Five variants, one per typia function family, with no shared base because each function has a different shape.
+ * @evidence contracts/common.md#prohibited-implementation-shortcuts It is a type and adds no runtime behavior; the runtime rejects an unknown `type` with an error instead of accepting it.
+ * @evidence contracts/common.md#meaningful-documentation The comment names the decorators that receive the serializer and the response each variant produces on a failed validation.
+ * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe JSON serialization and validation callbacks without native file or process representations.
+ */
 export declare namespace IResponseBodyStringifier {
+    /**
+     * Serializer generated from `typia.json.stringify`, without validation.
+     *
+     * @evidence contracts/common.md#principled-implementation The variant tags a function that serializes the data as it is, so a value of the wrong type is serialized as far as its shape allows without this variant performing validation.
+     * @evidence contracts/common.md#clear-and-simple-design A two-member record, the tag and the function.
+     * @evidence contracts/common.md#prohibited-implementation-shortcuts It is a type and adds no runtime behavior.
+     * @evidence contracts/common.md#meaningful-documentation The comment names the typia function the variant comes from.
+     * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe JSON serialization and validation callbacks without native file or process representations.
+     */
     interface IStringify<T> {
         type: "stringify";
+        /**
+         * The generated function of the variant, taking the response data.
+         *
+         * @evidence contracts/common.md#principled-implementation The transform generates the function for the return type of the route method, and the runtime uses the result as the response body as it is.
+         * @evidence contracts/common.md#clear-and-simple-design One function member.
+         * @evidence contracts/common.md#prohibited-implementation-shortcuts The function is generated from the type, and the runtime never edits its result.
+         * @evidence contracts/common.md#meaningful-documentation The comment states that the function is generated for the return type; its result is in the signature.
+         * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe JSON serialization and validation callbacks without native file or process representations.
+         */
         stringify: (input: T) => string;
     }
+    /**
+     * Serializer generated from `typia.json.isStringify`.
+     *
+     * @evidence contracts/common.md#principled-implementation The variant tags a function that returns the serialized text, or `null` when the data is not of the type; `null` becomes a 500 `InternalServerErrorException` with a fixed message.
+     * @evidence contracts/common.md#clear-and-simple-design A two-member record, the tag and the function.
+     * @evidence contracts/common.md#prohibited-implementation-shortcuts It is a type and adds no runtime behavior.
+     * @evidence contracts/common.md#meaningful-documentation The comment names the typia function the variant comes from.
+     * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe JSON serialization and validation callbacks without native file or process representations.
+     */
     interface IIs<T> {
         type: "is";
+        /**
+         * The generated function of the variant, taking the response data.
+         *
+         * @evidence contracts/common.md#principled-implementation The transform generates the function for the return type of the route method, and it returns the serialized text or `null`.
+         * @evidence contracts/common.md#clear-and-simple-design One function member.
+         * @evidence contracts/common.md#prohibited-implementation-shortcuts The function is generated from the type, and the runtime never edits its result.
+         * @evidence contracts/common.md#meaningful-documentation The comment states that the function is generated for the return type; its result is in the signature.
+         * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe JSON serialization and validation callbacks without native file or process representations.
+         */
         is: (input: T) => string | null;
     }
+    /**
+     * Serializer generated from `typia.json.assertStringify`.
+     *
+     * @evidence contracts/common.md#principled-implementation The variant tags a function that returns the serialized text or throws the `TypeGuardError` of typia, which becomes a 500 `InternalServerErrorException` with the path, reason, expected type, and value.
+     * @evidence contracts/common.md#clear-and-simple-design A two-member record, the tag and the function.
+     * @evidence contracts/common.md#prohibited-implementation-shortcuts It is a type and adds no runtime behavior.
+     * @evidence contracts/common.md#meaningful-documentation The comment names the typia function the variant comes from.
+     * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe JSON serialization and validation callbacks without native file or process representations.
+     */
     interface IAssert<T> {
         type: "assert";
+        /**
+         * The generated function of the variant, taking the response data.
+         *
+         * @evidence contracts/common.md#principled-implementation The transform generates the function for the return type of the route method, and it returns the serialized text or throws.
+         * @evidence contracts/common.md#clear-and-simple-design One function member.
+         * @evidence contracts/common.md#prohibited-implementation-shortcuts The function is generated from the type, and the runtime never edits its result.
+         * @evidence contracts/common.md#meaningful-documentation The comment states that the function is generated for the return type; its result is in the signature.
+         * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe JSON serialization and validation callbacks without native file or process representations.
+         */
         assert: (input: T) => string;
     }
+    /**
+     * Serializer generated from `typia.json.validateStringify`.
+     *
+     * @evidence contracts/common.md#principled-implementation The variant tags a function that returns the `IValidation` of the text; a failure becomes a 500 `InternalServerErrorException` carrying every error.
+     * @evidence contracts/common.md#clear-and-simple-design A two-member record, the tag and the function.
+     * @evidence contracts/common.md#prohibited-implementation-shortcuts It is a type and adds no runtime behavior.
+     * @evidence contracts/common.md#meaningful-documentation The comment names the typia function the variant comes from.
+     * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe JSON serialization and validation callbacks without native file or process representations.
+     */
     interface IValidate<T> {
         type: "validate";
+        /**
+         * The generated function of the variant, taking the response data.
+         *
+         * @evidence contracts/common.md#principled-implementation The transform generates the function for the return type of the route method, and it returns the validation result.
+         * @evidence contracts/common.md#clear-and-simple-design One function member.
+         * @evidence contracts/common.md#prohibited-implementation-shortcuts The function is generated from the type, and the runtime never edits its result.
+         * @evidence contracts/common.md#meaningful-documentation The comment states that the function is generated for the return type; its result is in the signature.
+         * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe JSON serialization and validation callbacks without native file or process representations.
+         */
         validate: (input: T) => IValidation<string>;
     }
+    /**
+     * Serializer generated from `typia.json.validateStringify`, for the
+     * `validate.log` mode.
+     *
+     * @evidence contracts/common.md#principled-implementation The variant tags the same function shape as `validate`, but a failure is passed to the logger registered with `TypedRoute.setValidateErrorLogger` and the response is `JSON.stringify` of the data, so a validation failure never changes the status.
+     * @evidence contracts/common.md#clear-and-simple-design A two-member record, the tag and the function.
+     * @evidence contracts/common.md#prohibited-implementation-shortcuts It is a type and adds no runtime behavior.
+     * @evidence contracts/common.md#meaningful-documentation The comment names the typia function the variant comes from.
+     * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe JSON serialization and validation callbacks without native file or process representations.
+     */
     interface IValidateLog<T> {
         type: "validate.log";
+        /**
+         * The generated function of the variant, taking the response data.
+         *
+         * @evidence contracts/common.md#principled-implementation The transform generates the function for the return type of the route method, and it returns the validation result.
+         * @evidence contracts/common.md#clear-and-simple-design One function member.
+         * @evidence contracts/common.md#prohibited-implementation-shortcuts The function is generated from the type, and the runtime never edits its result.
+         * @evidence contracts/common.md#meaningful-documentation The comment states that the function is generated for the return type; its result is in the signature.
+         * @evidenceExclude contracts/portability.md#os-neutral-implementation The variants describe JSON serialization and validation callbacks without native file or process representations.
+         */
         validate: (input: T) => IValidation<string>;
     }
 }

package/lib/typings/Creator.d.ts

@@ -1,3 +1,13 @@
+/**
+ * A class constructor: anything that can be called with `new` to build an
+ * instance of `T`.
+ *
+ * @evidence contracts/common.md#principled-implementation The construct signature with rest arguments is the standard TypeScript spelling of a class type.
+ * @evidence contracts/common.md#clear-and-simple-design One construct signature.
+ * @evidence contracts/common.md#prohibited-implementation-shortcuts It is a type and adds no runtime behavior.
+ * @evidence contracts/common.md#meaningful-documentation The comment states what the type stands for.
+ * @evidenceExclude contracts/portability.md#os-neutral-implementation The construct signature represents JavaScript class construction rather than a native resource boundary.
+ */
 export type Creator<T extends object> = {
     new (...args: any[]): T;
 };

package/lib/utils/ArrayUtil.d.ts

@@ -1,3 +1,24 @@
+/**
+ * Array helpers of the core runtime.
+ *
+ * @evidence contracts/common.md#principled-implementation The namespace holds the one membership helper the adapters use.
+ * @evidence contracts/common.md#clear-and-simple-design One function.
+ * @evidence contracts/common.md#prohibited-implementation-shortcuts It is a plain helper with no special cases.
+ * @evidence contracts/common.md#meaningful-documentation The comment states its purpose.
+ * @evidenceExclude contracts/portability.md#os-neutral-implementation Array membership uses JavaScript SameValueZero comparisons with no native filesystem or process access.
+ */
 export declare namespace ArrayUtil {
+    /**
+     * Reports whether the array contains every one of the items.
+     *
+     * Membership is decided by `Array.prototype.includes`, so an item that is
+     * `undefined` or `NaN` is found when the array holds it.
+     *
+     * @evidence contracts/common.md#principled-implementation `Array.prototype.includes` compares by SameValueZero, so the result is the conjunction over the items of membership, an item that is `undefined` or `NaN` is found when the array holds it, and no items yields true; an earlier `find` compared the found element with `undefined` and could not report an `undefined` member.
+     * @evidence contracts/common.md#clear-and-simple-design One `every` over `includes`.
+     * @evidence contracts/common.md#prohibited-implementation-shortcuts No item is special-cased.
+     * @evidence contracts/common.md#meaningful-documentation The comment states the conjunction and the comparison rule.
+     * @evidenceExclude contracts/portability.md#os-neutral-implementation Array membership uses JavaScript SameValueZero comparisons with no native filesystem or process access.
+     */
     function has<T>(array: T[], ...items: T[]): boolean;
 }

package/lib/utils/ArrayUtil.js

@@ -1,10 +1,31 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.ArrayUtil = void 0;
+/**
+ * Array helpers of the core runtime.
+ *
+ * @evidence contracts/common.md#principled-implementation The namespace holds the one membership helper the adapters use.
+ * @evidence contracts/common.md#clear-and-simple-design One function.
+ * @evidence contracts/common.md#prohibited-implementation-shortcuts It is a plain helper with no special cases.
+ * @evidence contracts/common.md#meaningful-documentation The comment states its purpose.
+ * @evidenceExclude contracts/portability.md#os-neutral-implementation Array membership uses JavaScript SameValueZero comparisons with no native filesystem or process access.
+ */
 var ArrayUtil;
 (function (ArrayUtil) {
+    /**
+     * Reports whether the array contains every one of the items.
+     *
+     * Membership is decided by `Array.prototype.includes`, so an item that is
+     * `undefined` or `NaN` is found when the array holds it.
+     *
+     * @evidence contracts/common.md#principled-implementation `Array.prototype.includes` compares by SameValueZero, so the result is the conjunction over the items of membership, an item that is `undefined` or `NaN` is found when the array holds it, and no items yields true; an earlier `find` compared the found element with `undefined` and could not report an `undefined` member.
+     * @evidence contracts/common.md#clear-and-simple-design One `every` over `includes`.
+     * @evidence contracts/common.md#prohibited-implementation-shortcuts No item is special-cased.
+     * @evidence contracts/common.md#meaningful-documentation The comment states the conjunction and the comparison rule.
+     * @evidenceExclude contracts/portability.md#os-neutral-implementation Array membership uses JavaScript SameValueZero comparisons with no native filesystem or process access.
+     */
     function has(array, ...items) {
-        return items.every((elem) => array.find((org) => org === elem) !== undefined);
+        return items.every((item) => array.includes(item));
     }
     ArrayUtil.has = has;
 })(ArrayUtil || (exports.ArrayUtil = ArrayUtil = {}));

package/lib/utils/ArrayUtil.js.map

@@ -1 +1 @@
-{"version":3,"file":"ArrayUtil.js","sourceRoot":"","sources":["../../src/utils/ArrayUtil.ts"],"names":[],"mappings":";;;AAAA,IAAiB,SAAS,CAMzB;AAND,WAAiB,SAAS;IACxB,SAAgB,GAAG,CAAI,KAAU,EAAE,GAAG,KAAU;QAC9C,OAAO,KAAK,CAAC,KAAK,CAChB,CAAC,IAAI,EAAE,EAAE,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC,GAAG,EAAE,EAAE,CAAC,GAAG,KAAK,IAAI,CAAC,KAAK,SAAS,CAC1D,CAAC;IACJ,CAAC;IAJe,UAAA,GAAG,MAIlB,CAAA;AACH,CAAC,EANgB,SAAS,aAAT,SAAS,GAAT,SAAS,QAMzB"}
+{"version":3,"file":"ArrayUtil.js","sourceRoot":"","sources":["../../src/utils/ArrayUtil.ts"],"names":[],"mappings":";;;AAAA;;;;;;;;GAQG;AACH,IAAiB,SAAS,CAgBzB;AAhBD,WAAiB,SAAS;IACxB;;;;;;;;;;;OAWG;IACH,SAAgB,GAAG,CAAI,KAAU,EAAE,GAAG,KAAU;QAC9C,OAAO,KAAK,CAAC,KAAK,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,KAAK,CAAC,QAAQ,CAAC,IAAI,CAAC,CAAC,CAAC;IACrD,CAAC;IAFe,UAAA,GAAG,MAElB,CAAA;AACH,CAAC,EAhBgB,SAAS,aAAT,SAAS,GAAT,SAAS,QAgBzB"}