typia 9.7.0 → 9.7.2

package/lib/tags/Pattern.d.mts

@@ -1,4 +1,22 @@
 import { TagBase } from "./TagBase";
+/**
+ * String pattern (regular expression) constraint tag.
+ *
+ * Validates that a string matches a specified regular expression pattern. Use
+ * this tag to enforce custom string formats through regex validation.
+ *
+ * Examples:
+ *
+ * ```ts
+ * type PhoneNumber = string & Pattern<"^\d{3}-\d{3}-\d{4}$">; // 123-456-7890
+ * type HexColor = string & Pattern<"^#[0-9A-Fa-f]{6}$">; // #FF5733
+ * ```
+ *
+ * Note: This tag is mutually exclusive with the Format tag. You cannot use both
+ * Pattern and Format on the same type.
+ *
+ * @author Jeongho Nam - https://github.com/samchon
+ */
 export type Pattern<Value extends string> = TagBase<{
     target: "string";
     kind: "pattern";

package/lib/tags/Pattern.d.ts

@@ -1,4 +1,22 @@
 import { TagBase } from "./TagBase";
+/**
+ * String pattern (regular expression) constraint tag.
+ *
+ * Validates that a string matches a specified regular expression pattern. Use
+ * this tag to enforce custom string formats through regex validation.
+ *
+ * Examples:
+ *
+ * ```ts
+ * type PhoneNumber = string & Pattern<"^\d{3}-\d{3}-\d{4}$">; // 123-456-7890
+ * type HexColor = string & Pattern<"^#[0-9A-Fa-f]{6}$">; // #FF5733
+ * ```
+ *
+ * Note: This tag is mutually exclusive with the Format tag. You cannot use both
+ * Pattern and Format on the same type.
+ *
+ * @author Jeongho Nam - https://github.com/samchon
+ */
 export type Pattern<Value extends string> = TagBase<{
     target: "string";
     kind: "pattern";

package/lib/tags/Sequence.d.mts

@@ -1,4 +1,31 @@
 import { TagBase } from "./TagBase";
+/**
+ * Assigns unique field numbers for Protocol Buffer serialization.
+ *
+ * In Protocol Buffer encoding, each field in a message must have a unique
+ * numeric identifier. The Sequence tag assigns these field numbers to
+ * TypeScript properties, enabling proper Protocol Buffer serialization and
+ * deserialization. Field numbers 1-15 require only one byte to encode, making
+ * them ideal for frequently used fields. Numbers 19000-19999 are reserved by
+ * the Protocol Buffer specification and should not be used.
+ *
+ * @author Jeongho Nam - https://github.com/samchon
+ * @example
+ *   ```typescript
+ *   interface User {
+ *     id: string & Sequence<1>;        // Most frequent field uses 1
+ *     email: string & Sequence<2>;     // Common fields use low numbers
+ *     createdAt: number & Sequence<3>;
+ *     metadata?: object & Sequence<10>; // Optional fields work too
+ *   }
+ *
+ *   // Generate Protocol Buffer message
+ *   const message = typia.protobuf.message<User>();
+ *   ```
+ *
+ * @template N - Field number (positive integer from 1 to 536,870,911, excluding
+ *   19000-19999)
+ */
 export type Sequence<N extends number> = TagBase<{
     target: "boolean" | "bigint" | "number" | "string" | "array" | "object";
     kind: "sequence";

package/lib/tags/Sequence.d.ts

@@ -1,4 +1,31 @@
 import { TagBase } from "./TagBase";
+/**
+ * Assigns unique field numbers for Protocol Buffer serialization.
+ *
+ * In Protocol Buffer encoding, each field in a message must have a unique
+ * numeric identifier. The Sequence tag assigns these field numbers to
+ * TypeScript properties, enabling proper Protocol Buffer serialization and
+ * deserialization. Field numbers 1-15 require only one byte to encode, making
+ * them ideal for frequently used fields. Numbers 19000-19999 are reserved by
+ * the Protocol Buffer specification and should not be used.
+ *
+ * @author Jeongho Nam - https://github.com/samchon
+ * @example
+ *   ```typescript
+ *   interface User {
+ *     id: string & Sequence<1>;        // Most frequent field uses 1
+ *     email: string & Sequence<2>;     // Common fields use low numbers
+ *     createdAt: number & Sequence<3>;
+ *     metadata?: object & Sequence<10>; // Optional fields work too
+ *   }
+ *
+ *   // Generate Protocol Buffer message
+ *   const message = typia.protobuf.message<User>();
+ *   ```
+ *
+ * @template N - Field number (positive integer from 1 to 536,870,911, excluding
+ *   19000-19999)
+ */
 export type Sequence<N extends number> = TagBase<{
     target: "boolean" | "bigint" | "number" | "string" | "array" | "object";
     kind: "sequence";

package/lib/tags/TagBase.d.mts

@@ -1,3 +1,24 @@
+/**
+ * Base type for all validation tags in typia.
+ *
+ * TagBase provides the foundation for all typia's validation tags. It attaches
+ * metadata to TypeScript types that typia's transformer processes at
+ * compile-time to generate optimized runtime validation code.
+ *
+ * @author Jeongho Nam - https://github.com/samchon
+ * @example
+ *   ```typescript
+ *   // Custom tag example
+ *   type MyCustomTag<Value extends number> = TagBase<{
+ *   target: "number";
+ *   kind: "MyCustom";
+ *   value: Value;
+ *   validate: `$input === ${Value}`;
+ *   }>;
+ *   ```
+ *
+ * @template Props - Tag properties that define validation behavior
+ */
 export type TagBase<Props extends TagBase.IProps<any, any, any, any, any, any>> = {
     /**
      * This is a dummy property for compilation.
@@ -7,33 +28,34 @@ export type TagBase<Props extends TagBase.IProps<any, any, any, any, any, any>>
     "typia.tag"?: Props;
 };
 export declare namespace TagBase {
+    /**
+     * Properties interface for validation tags.
+     *
+     * @author Jeongho Nam - https://github.com/samchon
+     */
     interface IProps<Target extends "boolean" | "bigint" | "number" | "string" | "array" | "object", Kind extends string, Value extends boolean | bigint | number | string | undefined, Validate extends string | {
         [key in Target]?: string;
     }, Exclusive extends boolean | string[], Schema extends object | undefined> {
         /**
          * Target type.
          *
-         * If user tries to adapt this tag to a different type, it would be a compile
-         * error.
+         * If user tries to adapt this tag to a different type, it would be a
+         * compile error.
          *
-         * For example, you've configured target type as `string`, but user adapted it
-         * onto a `number` type (`number & YourCustomTag<Value>`), then it would be
-         * blocked by TypeScript compiler.
+         * For example, you've configured target type as `string`, but user adapted
+         * it onto a `number` type (`number & YourCustomTag<Value>`), then it would
+         * be blocked by TypeScript compiler.
          */
         target: Target;
-        /**
-         * What kind of tag is this?
-         */
+        /** What kind of tag is this? */
         kind: Kind;
-        /**
-         * Value to be configured by user.
-         */
+        /** Value to be configured by user. */
         value: Value;
         /**
          * Validation script.
          *
-         * This script would be inserted into the generated validation function.
-         * In here script, target variable name must be `$input`. The variable name
+         * This script would be inserted into the generated validation function. In
+         * here script, target variable name must be `$input`. The variable name
          * `$input` would be transformed to the suitable when compilation.
          *
          * Also, If you've take a mistake on this script, compile error would be
@@ -46,15 +68,13 @@ export declare namespace TagBase {
          *
          * If this property configured as `true`, same {@link kind} tag cannot be
          * duplicated in the target type. Otherwise, if you've configured this
-         * property as string array, all of the {@link kind} value assigned
-         * tags cannot be compatible in the target type.
+         * property as string array, all of the {@link kind} value assigned tags
+         * cannot be compatible in the target type.
          *
          * @default false
          */
         exclusive?: Exclusive | string[];
-        /**
-         * Additional schema info assigned to the {@link IJsonSchema} object.
-         */
+        /** Additional schema info assigned to the {@link IJsonSchema} object. */
         schema?: Schema;
     }
 }

package/lib/tags/TagBase.d.ts

@@ -1,3 +1,24 @@
+/**
+ * Base type for all validation tags in typia.
+ *
+ * TagBase provides the foundation for all typia's validation tags. It attaches
+ * metadata to TypeScript types that typia's transformer processes at
+ * compile-time to generate optimized runtime validation code.
+ *
+ * @author Jeongho Nam - https://github.com/samchon
+ * @example
+ *   ```typescript
+ *   // Custom tag example
+ *   type MyCustomTag<Value extends number> = TagBase<{
+ *   target: "number";
+ *   kind: "MyCustom";
+ *   value: Value;
+ *   validate: `$input === ${Value}`;
+ *   }>;
+ *   ```
+ *
+ * @template Props - Tag properties that define validation behavior
+ */
 export type TagBase<Props extends TagBase.IProps<any, any, any, any, any, any>> = {
     /**
      * This is a dummy property for compilation.
@@ -7,33 +28,34 @@ export type TagBase<Props extends TagBase.IProps<any, any, any, any, any, any>>
     "typia.tag"?: Props;
 };
 export declare namespace TagBase {
+    /**
+     * Properties interface for validation tags.
+     *
+     * @author Jeongho Nam - https://github.com/samchon
+     */
     interface IProps<Target extends "boolean" | "bigint" | "number" | "string" | "array" | "object", Kind extends string, Value extends boolean | bigint | number | string | undefined, Validate extends string | {
         [key in Target]?: string;
     }, Exclusive extends boolean | string[], Schema extends object | undefined> {
         /**
          * Target type.
          *
-         * If user tries to adapt this tag to a different type, it would be a compile
-         * error.
+         * If user tries to adapt this tag to a different type, it would be a
+         * compile error.
          *
-         * For example, you've configured target type as `string`, but user adapted it
-         * onto a `number` type (`number & YourCustomTag<Value>`), then it would be
-         * blocked by TypeScript compiler.
+         * For example, you've configured target type as `string`, but user adapted
+         * it onto a `number` type (`number & YourCustomTag<Value>`), then it would
+         * be blocked by TypeScript compiler.
          */
         target: Target;
-        /**
-         * What kind of tag is this?
-         */
+        /** What kind of tag is this? */
         kind: Kind;
-        /**
-         * Value to be configured by user.
-         */
+        /** Value to be configured by user. */
         value: Value;
         /**
          * Validation script.
          *
-         * This script would be inserted into the generated validation function.
-         * In here script, target variable name must be `$input`. The variable name
+         * This script would be inserted into the generated validation function. In
+         * here script, target variable name must be `$input`. The variable name
          * `$input` would be transformed to the suitable when compilation.
          *
          * Also, If you've take a mistake on this script, compile error would be
@@ -46,15 +68,13 @@ export declare namespace TagBase {
          *
          * If this property configured as `true`, same {@link kind} tag cannot be
          * duplicated in the target type. Otherwise, if you've configured this
-         * property as string array, all of the {@link kind} value assigned
-         * tags cannot be compatible in the target type.
+         * property as string array, all of the {@link kind} value assigned tags
+         * cannot be compatible in the target type.
          *
          * @default false
          */
         exclusive?: Exclusive | string[];
-        /**
-         * Additional schema info assigned to the {@link IJsonSchema} object.
-         */
+        /** Additional schema info assigned to the {@link IJsonSchema} object. */
         schema?: Schema;
     }
 }

package/lib/tags/Type.d.mts

@@ -1,4 +1,31 @@
 import { TagBase } from "./TagBase";
+/**
+ * Type tag for specifying numeric bit-width representations.
+ *
+ * Constrains numeric types to specific bit-width formats used in systems
+ * programming and protocol buffers. Ensures numbers conform to
+ * platform-specific representations.
+ *
+ * Supported types:
+ *
+ * - `int32`: 32-bit signed integer (-2^31 to 2^31-1)
+ * - `uint32`: 32-bit unsigned integer (0 to 2^32-1)
+ * - `int64`: 64-bit signed integer (supports both bigint and number)
+ * - `uint64`: 64-bit unsigned integer (supports both bigint and number)
+ * - `float`: 32-bit floating point (single precision)
+ * - `double`: 64-bit floating point (double precision, default JS number)
+ *
+ * @author Jeongho Nam - https://github.com/samchon
+ * @example
+ *   ```typescript
+ *   type Score = number & Type<"int32">;      // -2,147,483,648 to 2,147,483,647
+ *   type UserId = number & Type<"uint32">;    // 0 to 4,294,967,295
+ *   type FileSize = bigint & Type<"int64">;   // Large file sizes
+ *   type Coordinate = number & Type<"double">; // High precision coordinates
+ *   ```
+ *
+ * @template Value - The numeric type representation
+ */
 export type Type<Value extends "int32" | "uint32" | "int64" | "uint64" | "float" | "double"> = TagBase<{
     target: Value extends "int64" | "uint64" ? "bigint" | "number" : "number";
     kind: "type";

package/lib/tags/Type.d.ts

@@ -1,4 +1,31 @@
 import { TagBase } from "./TagBase";
+/**
+ * Type tag for specifying numeric bit-width representations.
+ *
+ * Constrains numeric types to specific bit-width formats used in systems
+ * programming and protocol buffers. Ensures numbers conform to
+ * platform-specific representations.
+ *
+ * Supported types:
+ *
+ * - `int32`: 32-bit signed integer (-2^31 to 2^31-1)
+ * - `uint32`: 32-bit unsigned integer (0 to 2^32-1)
+ * - `int64`: 64-bit signed integer (supports both bigint and number)
+ * - `uint64`: 64-bit unsigned integer (supports both bigint and number)
+ * - `float`: 32-bit floating point (single precision)
+ * - `double`: 64-bit floating point (double precision, default JS number)
+ *
+ * @author Jeongho Nam - https://github.com/samchon
+ * @example
+ *   ```typescript
+ *   type Score = number & Type<"int32">;      // -2,147,483,648 to 2,147,483,647
+ *   type UserId = number & Type<"uint32">;    // 0 to 4,294,967,295
+ *   type FileSize = bigint & Type<"int64">;   // Large file sizes
+ *   type Coordinate = number & Type<"double">; // High precision coordinates
+ *   ```
+ *
+ * @template Value - The numeric type representation
+ */
 export type Type<Value extends "int32" | "uint32" | "int64" | "uint64" | "float" | "double"> = TagBase<{
     target: Value extends "int64" | "uint64" ? "bigint" | "number" : "number";
     kind: "type";

package/lib/tags/UniqueItems.d.mts

@@ -1,4 +1,24 @@
 import { TagBase } from "./TagBase";
+/**
+ * Unique items validation tag for arrays.
+ *
+ * Enforces that all items in an array are unique, preventing duplicate values.
+ * Uniqueness is determined using strict equality (===) for primitives and deep
+ * structural comparison for objects and arrays. This means two objects with the
+ * same properties and values are considered duplicates.
+ *
+ * @author Jeongho Nam - https://github.com/samchon
+ * @example
+ *   // Ensure all IDs are unique
+ *   type UserIds = number[] & UniqueItems;
+ *
+ * @example
+ *   // Prevent duplicate email addresses
+ *   type EmailList = string[] & UniqueItems;
+ *
+ * @template Value - Boolean flag to enable/disable uniqueness validation
+ *   (defaults to true)
+ */
 export type UniqueItems<Value extends boolean = true> = TagBase<{
     target: "array";
     kind: "uniqueItems";

package/lib/tags/UniqueItems.d.ts

@@ -1,4 +1,24 @@
 import { TagBase } from "./TagBase";
+/**
+ * Unique items validation tag for arrays.
+ *
+ * Enforces that all items in an array are unique, preventing duplicate values.
+ * Uniqueness is determined using strict equality (===) for primitives and deep
+ * structural comparison for objects and arrays. This means two objects with the
+ * same properties and values are considered duplicates.
+ *
+ * @author Jeongho Nam - https://github.com/samchon
+ * @example
+ *   // Ensure all IDs are unique
+ *   type UserIds = number[] & UniqueItems;
+ *
+ * @example
+ *   // Prevent duplicate email addresses
+ *   type EmailList = string[] & UniqueItems;
+ *
+ * @template Value - Boolean flag to enable/disable uniqueness validation
+ *   (defaults to true)
+ */
 export type UniqueItems<Value extends boolean = true> = TagBase<{
     target: "array";
     kind: "uniqueItems";

package/lib/tags/internal/FormatCheatSheet.d.mts

@@ -1,6 +1,4 @@
-/**
- * @reference https://github.dev/ajv-validator/ajv-formats/blob/master/src/formats.ts
- */
+/** @reference https://github.dev/ajv-validator/ajv-formats/blob/master/src/formats.ts */
 export declare const FormatCheatSheet: {
     readonly byte: "/^(?:[A-Za-z0-9+/]{4})*(?:[A-Za-z0-9+/]{2}==|[A-Za-z0-9+/]{3}=)?$/gm.test($input)";
     readonly password: "true";

package/lib/tags/internal/FormatCheatSheet.d.ts

@@ -1,6 +1,4 @@
-/**
- * @reference https://github.dev/ajv-validator/ajv-formats/blob/master/src/formats.ts
- */
+/** @reference https://github.dev/ajv-validator/ajv-formats/blob/master/src/formats.ts */
 export declare const FormatCheatSheet: {
     readonly byte: "/^(?:[A-Za-z0-9+/]{4})*(?:[A-Za-z0-9+/]{2}==|[A-Za-z0-9+/]{3}=)?$/gm.test($input)";
     readonly password: "true";

package/lib/tags/internal/FormatCheatSheet.js

@@ -2,9 +2,7 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.FormatCheatSheet = void 0;
 const RegexCall = (text) => `${text}.test($input)`;
-/**
- * @reference https://github.dev/ajv-validator/ajv-formats/blob/master/src/formats.ts
- */
+/** @reference https://github.dev/ajv-validator/ajv-formats/blob/master/src/formats.ts */
 exports.FormatCheatSheet = {
     // SPECIAL CHARACTERS
     byte: RegexCall(`/^(?:[A-Za-z0-9+/]{4})*(?:[A-Za-z0-9+/]{2}==|[A-Za-z0-9+/]{3}=)?$/gm`),

package/lib/tags/internal/FormatCheatSheet.js.map

@@ -1 +1 @@
-{"version":3,"file":"FormatCheatSheet.js","sourceRoot":"","sources":["../../../src/tags/internal/FormatCheatSheet.ts"],"names":[],"mappings":";;;AAAA,MAAM,SAAS,GAAG,CAAsB,IAAU,EAAE,EAAE,CACpD,GAAG,IAAI,eAAwB,CAAC;AAElC;;GAEG;AACU,QAAA,gBAAgB,GAAG;IAC9B,qBAAqB;IACrB,IAAI,EAAE,SAAS,CACb,sEAAsE,CACvE;IACD,QAAQ,EAAE,MAAM;IAChB,KAAK,EAAE,gFAAgF;IACvF,IAAI,EAAE,SAAS,CACb,gEAAgE,CACjE;IAED,YAAY;IACZ,KAAK,EAAE,SAAS,CACd,gJAAgJ,CACjJ;IACD,QAAQ,EAAE,SAAS,CACjB,4GAA4G,CAC7G;IACD,WAAW,EAAE,SAAS,CACpB,4IAA4I,CAC7I;IACD,cAAc,EAAE,SAAS,CACvB,+FAA+F,CAChG;IACD,GAAG,EAAE,SAAS,CACZ,+DAA+D,CAChE;IACD,eAAe,EAAE,SAAS,CACxB,+DAA+D,CAChE;IACD,IAAI,EAAE,SAAS,CACb,8FAA8F,CAC/F;IACD,IAAI,EAAE,SAAS,CACb,o/BAAo/B,CACr/B;IACD,GAAG,EAAE,GAAG,SAAS,CAAC,SAAS,CAAC,OAAO,SAAS,CAC1C,oqCAAoqC,CACrqC,EAAE;IACH,eAAe,EAAE,SAAS,CACxB,8qCAA8qC,CAC/qC;IACD,cAAc,EAAE,SAAS,CACvB,8LAA8L,CAC/L;IACD,GAAG,EAAE,SAAS,CACZ,+fAA+f,CAChgB;IAED,aAAa;IACb,WAAW,EAAE,SAAS,CACpB,8JAA8J,CAC/J;IACD,IAAI,EAAE,SAAS,CAAC,uDAAuD,CAAC;IACxE,IAAI,EAAE,SAAS,CACb,sGAAsG,CACvG;IACD,QAAQ,EAAE,SAAS,CACjB,kFAAkF,CACnF;IAED,WAAW;IACX,cAAc,EAAE,SAAS,CAAC,8BAA8B,CAAC;IACzD,uBAAuB,EAAE,SAAS,CAChC,qDAAqD,CACtD;CACO,CAAC"}
+{"version":3,"file":"FormatCheatSheet.js","sourceRoot":"","sources":["../../../src/tags/internal/FormatCheatSheet.ts"],"names":[],"mappings":";;;AAAA,MAAM,SAAS,GAAG,CAAsB,IAAU,EAAE,EAAE,CACpD,GAAG,IAAI,eAAwB,CAAC;AAElC,yFAAyF;AAC5E,QAAA,gBAAgB,GAAG;IAC9B,qBAAqB;IACrB,IAAI,EAAE,SAAS,CACb,sEAAsE,CACvE;IACD,QAAQ,EAAE,MAAM;IAChB,KAAK,EAAE,gFAAgF;IACvF,IAAI,EAAE,SAAS,CACb,gEAAgE,CACjE;IAED,YAAY;IACZ,KAAK,EAAE,SAAS,CACd,gJAAgJ,CACjJ;IACD,QAAQ,EAAE,SAAS,CACjB,4GAA4G,CAC7G;IACD,WAAW,EAAE,SAAS,CACpB,4IAA4I,CAC7I;IACD,cAAc,EAAE,SAAS,CACvB,+FAA+F,CAChG;IACD,GAAG,EAAE,SAAS,CACZ,+DAA+D,CAChE;IACD,eAAe,EAAE,SAAS,CACxB,+DAA+D,CAChE;IACD,IAAI,EAAE,SAAS,CACb,8FAA8F,CAC/F;IACD,IAAI,EAAE,SAAS,CACb,o/BAAo/B,CACr/B;IACD,GAAG,EAAE,GAAG,SAAS,CAAC,SAAS,CAAC,OAAO,SAAS,CAC1C,oqCAAoqC,CACrqC,EAAE;IACH,eAAe,EAAE,SAAS,CACxB,8qCAA8qC,CAC/qC;IACD,cAAc,EAAE,SAAS,CACvB,8LAA8L,CAC/L;IACD,GAAG,EAAE,SAAS,CACZ,+fAA+f,CAChgB;IAED,aAAa;IACb,WAAW,EAAE,SAAS,CACpB,8JAA8J,CAC/J;IACD,IAAI,EAAE,SAAS,CAAC,uDAAuD,CAAC;IACxE,IAAI,EAAE,SAAS,CACb,sGAAsG,CACvG;IACD,QAAQ,EAAE,SAAS,CACjB,kFAAkF,CACnF;IAED,WAAW;IACX,cAAc,EAAE,SAAS,CAAC,8BAA8B,CAAC;IACzD,uBAAuB,EAAE,SAAS,CAChC,qDAAqD,CACtD;CACO,CAAC"}

package/lib/tags/internal/FormatCheatSheet.mjs

@@ -1,7 +1,5 @@
 const RegexCall = (text) => `${text}.test($input)`;
-/**
- * @reference https://github.dev/ajv-validator/ajv-formats/blob/master/src/formats.ts
- */
+/** @reference https://github.dev/ajv-validator/ajv-formats/blob/master/src/formats.ts */
 const FormatCheatSheet = {
     // SPECIAL CHARACTERS
     byte: RegexCall(`/^(?:[A-Za-z0-9+/]{4})*(?:[A-Za-z0-9+/]{2}==|[A-Za-z0-9+/]{3}=)?$/gm`),

package/lib/transformers/ITransformOptions.d.mts

@@ -2,16 +2,20 @@ export interface ITransformOptions {
     /**
      * Whether to validate finite number or not.
      *
-     * If configured true, number typed values would be validated by Number.isNaN().
+     * If configured true, number typed values would be validated by
+     * Number.isNaN().
      *
-     * However, whatever you configure, it would be ignored when marshaling or parsing.
+     * However, whatever you configure, it would be ignored when marshaling or
+     * parsing.
      *
-     *   - when marshaling, always be true
-     *     - assertStringify()
-     *     - validateEncode()
-     *   - when parsing, always be false
-     *     - assertParse()
-     *     - isDecode()
+     * - When marshaling, always be true
+     *
+     *   - AssertStringify()
+     *   - ValidateEncode()
+     * - When parsing, always be false
+     *
+     *   - AssertParse()
+     *   - IsDecode()
      *
      * @default false
      */
@@ -19,17 +23,20 @@ export interface ITransformOptions {
     /**
      * Whether to validate finite number or not.
      *
-     * If configured true, number typed values would be validated by Number.isFinite().
+     * If configured true, number typed values would be validated by
+     * Number.isFinite().
      *
      * However, whatever you configure, it can be ignored in below case.
      *
-     *   - when `finite` option is true, this option would be ignored
-     *   - when marshaling, always be true
-     *     - assertStringify()
-     *     - validateEncode()
-     *   - when parsing, always be false
-     *     - assertParse()
-     *     - isDecode()
+     * - When `finite` option is true, this option would be ignored
+     * - When marshaling, always be true
+     *
+     *   - AssertStringify()
+     *   - ValidateEncode()
+     * - When parsing, always be false
+     *
+     *   - AssertParse()
+     *   - IsDecode()
      *
      * @default false
      */
@@ -37,7 +44,8 @@ export interface ITransformOptions {
     /**
      * Whether to validate functional type or not.
      *
-     * However, whatever you configure, it becomes false when marshaling or parsing.
+     * However, whatever you configure, it becomes false when marshaling or
+     * parsing.
      *
      * @default false
      */
@@ -46,8 +54,8 @@ export interface ITransformOptions {
      * Whether to check undefined value or not.
      *
      * JavaScript can assign `undefined` value to a specific property and it is an
-     * issue when validating without allowing superfluous properties. Should undefined
-     * value assigned superfluous property be allowed or not?
+     * issue when validating without allowing superfluous properties. Should
+     * undefined value assigned superfluous property be allowed or not?
      *
      * Note that, this option only works on {@link equals} function. Other function
      * like {@link assertEquals} or {@link validateEquals} would ignore this option

package/lib/transformers/ITransformOptions.d.ts

@@ -2,16 +2,20 @@ export interface ITransformOptions {
     /**
      * Whether to validate finite number or not.
      *
-     * If configured true, number typed values would be validated by Number.isNaN().
+     * If configured true, number typed values would be validated by
+     * Number.isNaN().
      *
-     * However, whatever you configure, it would be ignored when marshaling or parsing.
+     * However, whatever you configure, it would be ignored when marshaling or
+     * parsing.
      *
-     *   - when marshaling, always be true
-     *     - assertStringify()
-     *     - validateEncode()
-     *   - when parsing, always be false
-     *     - assertParse()
-     *     - isDecode()
+     * - When marshaling, always be true
+     *
+     *   - AssertStringify()
+     *   - ValidateEncode()
+     * - When parsing, always be false
+     *
+     *   - AssertParse()
+     *   - IsDecode()
      *
      * @default false
      */
@@ -19,17 +23,20 @@ export interface ITransformOptions {
     /**
      * Whether to validate finite number or not.
      *
-     * If configured true, number typed values would be validated by Number.isFinite().
+     * If configured true, number typed values would be validated by
+     * Number.isFinite().
      *
      * However, whatever you configure, it can be ignored in below case.
      *
-     *   - when `finite` option is true, this option would be ignored
-     *   - when marshaling, always be true
-     *     - assertStringify()
-     *     - validateEncode()
-     *   - when parsing, always be false
-     *     - assertParse()
-     *     - isDecode()
+     * - When `finite` option is true, this option would be ignored
+     * - When marshaling, always be true
+     *
+     *   - AssertStringify()
+     *   - ValidateEncode()
+     * - When parsing, always be false
+     *
+     *   - AssertParse()
+     *   - IsDecode()
      *
      * @default false
      */
@@ -37,7 +44,8 @@ export interface ITransformOptions {
     /**
      * Whether to validate functional type or not.
      *
-     * However, whatever you configure, it becomes false when marshaling or parsing.
+     * However, whatever you configure, it becomes false when marshaling or
+     * parsing.
      *
      * @default false
      */
@@ -46,8 +54,8 @@ export interface ITransformOptions {
      * Whether to check undefined value or not.
      *
      * JavaScript can assign `undefined` value to a specific property and it is an
-     * issue when validating without allowing superfluous properties. Should undefined
-     * value assigned superfluous property be allowed or not?
+     * issue when validating without allowing superfluous properties. Should
+     * undefined value assigned superfluous property be allowed or not?
      *
      * Note that, this option only works on {@link equals} function. Other function
      * like {@link assertEquals} or {@link validateEquals} would ignore this option