@autobe/agent 0.30.0-dev.20260315 → 0.30.0

package/lib/orchestrate/interface/utils/AutoBeJsonSchemaValidator.js

@@ -61,35 +61,35 @@ var AutoBeJsonSchemaValidator;
                 path: props.path,
                 expected: "At most one dot(.) character allowed in type name",
                 value: transform(props.key),
-                description: utils_1.StringUtil.trim `
-          JSON schema type name allows at most one dot(.) character to separate
-          module name and interface name.
-
-          However, current key name ${transform(JSON.stringify(props.key))}
-          contains multiple dot(.) characters (${elements.length - 1} times).
-
-          Change it to a valid type name with at most one dot(.) character at the next time.
-          Note that, this is not a recommendation, but an instruction you must follow.
+                description: utils_1.StringUtil.trim `
+          JSON schema type name allows at most one dot(.) character to separate
+          module name and interface name.
+
+          However, current key name ${transform(JSON.stringify(props.key))}
+          contains multiple dot(.) characters (${elements.length - 1} times).
+
+          Change it to a valid type name with at most one dot(.) character at the next time.
+          Note that, this is not a recommendation, but an instruction you must follow.
         `,
             });
         if (elements.every(utils_2.NamingConvention.variable) === false)
             props.errors.push({
                 path: props.path,
-                expected: utils_1.StringUtil.trim `
-          Valid variable name
-
-          ${elements.map((s) => `- ${s}: ${utils_2.NamingConvention.variable(s) ? "valid" : "invalid"}`).join("\n")}
+                expected: utils_1.StringUtil.trim `
+          Valid variable name
+
+          ${elements.map((s) => `- ${s}: ${utils_2.NamingConvention.variable(s) ? "valid" : "invalid"}`).join("\n")}
         `,
                 value: transform(props.key),
-                description: utils_1.StringUtil.trim `
-          JSON schema type name must be a valid variable name.
-
-          Even though JSON schema type name allows dot(.) character, but
-          each segment separated by dot(.) must be a valid variable name.
-
-          Current key name ${transform(JSON.stringify(props.key))} is not valid.
-          Change it to a valid variable name at the next time.
-          Note that, this is not a recommendation, but an instruction you must follow.
+                description: utils_1.StringUtil.trim `
+          JSON schema type name must be a valid variable name.
+
+          Even though JSON schema type name allows dot(.) character, but
+          each segment separated by dot(.) must be a valid variable name.
+
+          Current key name ${transform(JSON.stringify(props.key))} is not valid.
+          Change it to a valid variable name at the next time.
+          Note that, this is not a recommendation, but an instruction you must follow.
         `,
             });
         if (props.key.endsWith(".IPage")) {
@@ -98,16 +98,16 @@ var AutoBeJsonSchemaValidator;
                 path: props.path,
                 expected: `"IPage" must be followed by another interface name. Use ${transform(JSON.stringify(expected))} instead.`,
                 value: transform(props.key),
-                description: utils_1.StringUtil.trim `
-          "IPage" is a reserved type name for pagination response.
-          The pagination data type name must be post-fixed after "IPage".
-          
-          However, you've defined ${transform(JSON.stringify(props.key))}, 
-          post-fixing ".IPage" after the pagination data type name.
-
-          Change it to a valid pagination type name to be
-          ${transform(JSON.stringify(expected))} at the next time. 
-          Note that, this is not a recommendation, but an instruction you must follow.
+                description: utils_1.StringUtil.trim `
+          "IPage" is a reserved type name for pagination response.
+          The pagination data type name must be post-fixed after "IPage".
+          
+          However, you've defined ${transform(JSON.stringify(props.key))}, 
+          post-fixing ".IPage" after the pagination data type name.
+
+          Change it to a valid pagination type name to be
+          ${transform(JSON.stringify(expected))} at the next time. 
+          Note that, this is not a recommendation, but an instruction you must follow.
         `,
             });
         }
@@ -116,13 +116,13 @@ var AutoBeJsonSchemaValidator;
                 path: props.path,
                 expected: `"IPageIRequest" is a mistake. Use "IPage.IRequest" instead.`,
                 value: transform(props.key),
-                description: utils_1.StringUtil.trim `
-          You've taken a mistake that defines "${transform("IPageIRequest")}" as a type name.
-          However, as you've intended to define a pagination request type,
-          the correct type name is "${transform("IPage.IRequest")}" instead of "${transform("IPageIRequest")}".
-
-          Change it to "${transform("IPage.IRequest")}" at the next time.
-          Note that, this is not a recommendation, but an instruction you must follow.
+                description: utils_1.StringUtil.trim `
+          You've taken a mistake that defines "${transform("IPageIRequest")}" as a type name.
+          However, as you've intended to define a pagination request type,
+          the correct type name is "${transform("IPage.IRequest")}" instead of "${transform("IPageIRequest")}".
+
+          Change it to "${transform("IPage.IRequest")}" at the next time.
+          Note that, this is not a recommendation, but an instruction you must follow.
         `,
             });
         if (props.key.startsWith("IPage") &&
@@ -138,19 +138,19 @@ var AutoBeJsonSchemaValidator;
                 path: props.path,
                 expected: `Interface name starting with 'I' even after 'IPage': ${JSON.stringify(expected)}`,
                 value: transform(props.key),
-                description: utils_1.StringUtil.trim `
-          JSON schema type name must be an interface name starting with 'I'.
-          Even though JSON schema type name allows dot(.) character, but
-          each segment separated by dot(.) must be an interface name starting
-          with 'I'.
-
-          Even in the case of pagination response, after 'IPage' prefix,
-          the remaining part must be an interface name starting with 'I'.
-
-          Current key name ${JSON.stringify(props.key)} is not valid. Change
-          it to a valid interface name to be  ${JSON.stringify(expected)},
-          or change it to another valid interface name at the next time.
-          Note that, this is not a recommendation, but an instruction you must follow.
+                description: utils_1.StringUtil.trim `
+          JSON schema type name must be an interface name starting with 'I'.
+          Even though JSON schema type name allows dot(.) character, but
+          each segment separated by dot(.) must be an interface name starting
+          with 'I'.
+
+          Even in the case of pagination response, after 'IPage' prefix,
+          the remaining part must be an interface name starting with 'I'.
+
+          Current key name ${JSON.stringify(props.key)} is not valid. Change
+          it to a valid interface name to be  ${JSON.stringify(expected)},
+          or change it to another valid interface name at the next time.
+          Note that, this is not a recommendation, but an instruction you must follow.
         `,
             });
         }
@@ -162,17 +162,17 @@ var AutoBeJsonSchemaValidator;
                 path: props.path,
                 expected: `Interface name starting with 'I': ${JSON.stringify(expected)}`,
                 value: transform(props.key),
-                description: utils_1.StringUtil.trim `
-          JSON schema type name must be an interface name starting with 'I'.
-          Even though JSON schema type name allows dot(.) character, but
-          each segment separated by dot(.) must be an interface name starting
-          with 'I'.
-
-          Current key name ${transform(JSON.stringify(props.key))} is not valid. 
-          Change it to a valid interface name to be ${transform(JSON.stringify(expected))}, 
-          or change it to another valid interface name at the next time.
-
-          Note that, this is not a recommendation, but an instruction you must follow.
+                description: utils_1.StringUtil.trim `
+          JSON schema type name must be an interface name starting with 'I'.
+          Even though JSON schema type name allows dot(.) character, but
+          each segment separated by dot(.) must be an interface name starting
+          with 'I'.
+
+          Current key name ${transform(JSON.stringify(props.key))} is not valid. 
+          Change it to a valid interface name to be ${transform(JSON.stringify(expected))}, 
+          or change it to another valid interface name at the next time.
+
+          Note that, this is not a recommendation, but an instruction you must follow.
         `,
             });
         }
@@ -186,27 +186,27 @@ var AutoBeJsonSchemaValidator;
                 path: props.path,
                 expected: JSON.stringify(`${elements[0].replace("Session", "")}.${elements[1]}`),
                 value: transform(props.key),
-                description: utils_1.StringUtil.trim `
-          You have attached ${elements[1]} to a Session type ${transform(JSON.stringify(props.key))},
-          but this is architecturally incorrect.
-
-          In production authentication systems, Actor and Session are separate concepts:
-          - **Actor** (e.g., User, Seller, Admin): The persistent user identity that performs
-            authentication actions - joining (registering), logging in, and receiving authorized tokens.
-          - **Session** (e.g., UserSession, SellerSession): The temporary authentication state that
-            tracks active login instances. Sessions are CREATED as a result of join/login operations,
-            but they do not perform these actions themselves.
-
-          Think about it semantically: An ACTOR joins the system and logs in. A SESSION is merely
-          a record that gets created when the actor authenticates. It makes no sense for a session
-          to "join" or "login" - only actors do that.
-
-          Therefore, authentication-related DTO types (IJoin, ILogin, IAuthorized, IRefresh) MUST
-          be attached to the Actor type, NEVER to the Session type.
-
-          Change ${transform(JSON.stringify(props.key))} to ${transform(JSON.stringify(`${elements[0].replace("Session", "")}.${elements[1]}`))} at the next time.
-
-          Note that, this is not a recommendation, but an instruction you must follow.
+                description: utils_1.StringUtil.trim `
+          You have attached ${elements[1]} to a Session type ${transform(JSON.stringify(props.key))},
+          but this is architecturally incorrect.
+
+          In production authentication systems, Actor and Session are separate concepts:
+          - **Actor** (e.g., User, Seller, Admin): The persistent user identity that performs
+            authentication actions - joining (registering), logging in, and receiving authorized tokens.
+          - **Session** (e.g., UserSession, SellerSession): The temporary authentication state that
+            tracks active login instances. Sessions are CREATED as a result of join/login operations,
+            but they do not perform these actions themselves.
+
+          Think about it semantically: An ACTOR joins the system and logs in. A SESSION is merely
+          a record that gets created when the actor authenticates. It makes no sense for a session
+          to "join" or "login" - only actors do that.
+
+          Therefore, authentication-related DTO types (IJoin, ILogin, IAuthorized, IRefresh) MUST
+          be attached to the Actor type, NEVER to the Session type.
+
+          Change ${transform(JSON.stringify(props.key))} to ${transform(JSON.stringify(`${elements[0].replace("Session", "")}.${elements[1]}`))} at the next time.
+
+          Note that, this is not a recommendation, but an instruction you must follow.
         `,
             });
     };
@@ -267,20 +267,20 @@ var AutoBeJsonSchemaValidator;
                             .map((s) => JSON.stringify(`#/components/schemas/${s}`))
                             .join(" | "),
                         value: key,
-                        description: utils_1.StringUtil.trim `
-              You've referenced an authorization-related type ${JSON.stringify(key)}
-              that is not used in any operation's requestBody or responseBody.
-
-              Authorization-related types must be used in at least one operation's
-              requestBody or responseBody. Make sure to use the type appropriately
-              in your API design.
-
-              Existing authorization-related types used in operations are:
+                        description: utils_1.StringUtil.trim `
+              You've referenced an authorization-related type ${JSON.stringify(key)}
+              that is not used in any operation's requestBody or responseBody.
+
+              Authorization-related types must be used in at least one operation's
+              requestBody or responseBody. Make sure to use the type appropriately
+              in your API design.
+
+              Existing authorization-related types used in operations are:
               - ${Array.from(candidates)
                             .map((s) => `#/components/schemas/${s}`)
-                            .join("\n- ")}
-
-              Note that, this is not a recommendation, but an instruction you must follow.
+                            .join("\n- ")}
+
+              Note that, this is not a recommendation, but an instruction you must follow.
             `,
                     });
             },
@@ -295,61 +295,61 @@ var AutoBeJsonSchemaValidator;
         });
         if (utils_1.AutoBeOpenApiTypeChecker.isReference(props.schema) &&
             props.schema.$ref === `#/components/schemas/${props.typeName}`)
-            report(utils_1.StringUtil.trim `
-        You have defined a nonsensible type like below:
-
-        \`\`\`typescript
-        type ${props.typeName} = ${props.typeName};
-        \`\`\`
-
-        This is an infinite recursive type definition that cannot exist in any
-        programming language. A type cannot be defined as itself - this creates
-        a circular definition with no base case, making the type impossible to
-        instantiate or validate.
-
-        If you need tree or graph structures, use explicit relationships with
-        ID references (e.g., parentId: string) instead of recursive type definitions.
-        Remove the self-reference and redesign the schema at the next time.
-        Note that, this is not a recommendation, but an instruction you must follow.
+            report(utils_1.StringUtil.trim `
+        You have defined a nonsensible type like below:
+
+        \`\`\`typescript
+        type ${props.typeName} = ${props.typeName};
+        \`\`\`
+
+        This is an infinite recursive type definition that cannot exist in any
+        programming language. A type cannot be defined as itself - this creates
+        a circular definition with no base case, making the type impossible to
+        instantiate or validate.
+
+        If you need tree or graph structures, use explicit relationships with
+        ID references (e.g., parentId: string) instead of recursive type definitions.
+        Remove the self-reference and redesign the schema at the next time.
+        Note that, this is not a recommendation, but an instruction you must follow.
       `);
         else if (utils_1.AutoBeOpenApiTypeChecker.isArray(props.schema) &&
             utils_1.AutoBeOpenApiTypeChecker.isReference(props.schema.items) &&
             props.schema.items.$ref === `#/components/schemas/${props.typeName}`)
-            report(utils_1.StringUtil.trim `
-        You have defined a nonsensible type like below:
-
-        \`\`\`typescript
-        type ${props.typeName} = Array<${props.typeName}>;
-        \`\`\`
-
-        This is an infinite recursive array type that cannot exist in any
-        programming language. An array of itself creates a circular definition
-        with no base case, making the type impossible to instantiate or validate.
-
-        If you need nested structures, define explicit depth levels with separate
-        types, or use parent-child relationships with ID references.
-        Remove the self-reference and redesign the schema at the next time.
-        Note that, this is not a recommendation, but an instruction you must follow.
+            report(utils_1.StringUtil.trim `
+        You have defined a nonsensible type like below:
+
+        \`\`\`typescript
+        type ${props.typeName} = Array<${props.typeName}>;
+        \`\`\`
+
+        This is an infinite recursive array type that cannot exist in any
+        programming language. An array of itself creates a circular definition
+        with no base case, making the type impossible to instantiate or validate.
+
+        If you need nested structures, define explicit depth levels with separate
+        types, or use parent-child relationships with ID references.
+        Remove the self-reference and redesign the schema at the next time.
+        Note that, this is not a recommendation, but an instruction you must follow.
       `);
         else if (utils_1.AutoBeOpenApiTypeChecker.isOneOf(props.schema) &&
             props.schema.oneOf.some((v) => utils_1.AutoBeOpenApiTypeChecker.isReference(v) &&
                 v.$ref === `#/components/schemas/${props.typeName}`) === true)
-            report(utils_1.StringUtil.trim `
-        You have defined a nonsensible type like below:
-
-        \`\`\`typescript
-        type ${props.typeName} = ${props.typeName} | ...;
-        \`\`\`
-
-        This is an infinite recursive union type that cannot exist in any
-        programming language. A union that includes itself as a variant creates
-        a circular definition with no base case, making the type impossible to
-        instantiate or validate.
-
-        If you need polymorphic hierarchies, define separate concrete types for
-        each variant without including the union type itself as a variant.
-        Remove the self-reference and redesign the schema at the next time.
-        Note that, this is not a recommendation, but an instruction you must follow.
+            report(utils_1.StringUtil.trim `
+        You have defined a nonsensible type like below:
+
+        \`\`\`typescript
+        type ${props.typeName} = ${props.typeName} | ...;
+        \`\`\`
+
+        This is an infinite recursive union type that cannot exist in any
+        programming language. A union that includes itself as a variant creates
+        a circular definition with no base case, making the type impossible to
+        instantiate or validate.
+
+        If you need polymorphic hierarchies, define separate concrete types for
+        each variant without including the union type itself as a variant.
+        Remove the self-reference and redesign the schema at the next time.
+        Note that, this is not a recommendation, but an instruction you must follow.
       `);
         else if (utils_1.AutoBeOpenApiTypeChecker.isObject(props.schema) &&
             props.schema.properties &&
@@ -357,28 +357,28 @@ var AutoBeJsonSchemaValidator;
             Object.entries(props.schema.properties).some(([k, v]) => utils_1.AutoBeOpenApiTypeChecker.isReference(v) &&
                 v.$ref === `#/components/schemas/${props.typeName}` &&
                 props.schema.required.includes(k)))
-            report(utils_1.StringUtil.trim `
-        You have defined a nonsensible type like below:
-
-        \`\`\`typescript
-        interface ${props.typeName} {
-          someProperty: ${props.typeName}; // required, non-nullable
-        }
-        \`\`\`
-
-        This is an infinite recursive object type that cannot exist in any
-        programming language. A required non-nullable property referencing its
-        own type creates a circular definition with no base case, making the
-        type impossible to instantiate.
-
-        To create an instance of ${props.typeName}, you would need an instance of ${props.typeName},
-        which requires another instance of ${props.typeName}, infinitely. This is logically
-        impossible.
-
-        If you need parent-child or graph relationships, make the self-referencing
-        property either nullable or optional, or use ID references (e.g., parentId: string).
-        Remove the required self-reference and redesign the schema at the next time.
-        Note that, this is not a recommendation, but an instruction you must follow.
+            report(utils_1.StringUtil.trim `
+        You have defined a nonsensible type like below:
+
+        \`\`\`typescript
+        interface ${props.typeName} {
+          someProperty: ${props.typeName}; // required, non-nullable
+        }
+        \`\`\`
+
+        This is an infinite recursive object type that cannot exist in any
+        programming language. A required non-nullable property referencing its
+        own type creates a circular definition with no base case, making the
+        type impossible to instantiate.
+
+        To create an instance of ${props.typeName}, you would need an instance of ${props.typeName},
+        which requires another instance of ${props.typeName}, infinitely. This is logically
+        impossible.
+
+        If you need parent-child or graph relationships, make the self-referencing
+        property either nullable or optional, or use ID references (e.g., parentId: string).
+        Remove the required self-reference and redesign the schema at the next time.
+        Note that, this is not a recommendation, but an instruction you must follow.
       `);
     };
     const validateObjectType = (props) => {
@@ -397,23 +397,23 @@ var AutoBeJsonSchemaValidator;
                     path: props.path,
                     expected: `AutoBeOpenApi.IJsonSchemaDescriptive.IObject`,
                     value: schema,
-                    description: utils_1.StringUtil.trim `
-            Root schema types (used in requestBody or responseBody of operations)
-            must be defined as object types. 
-            
-            This is the rule enforced to ensure consistent API design and to facilitate easier data handling.
-            Even though you think that defining a non-object type is more convenient for your specific use case,
-            just follow the rule without any resistance.
-
-            Note that, this is not a recommendation, but an instruction you must follow.
-
-            If current type is hard to be defined as an object type, just wrap it in an object type like below:
-
-            \`\`\`typescript
-            {
-              value: T;
-            }
-            \`\`\`
+                    description: utils_1.StringUtil.trim `
+            Root schema types (used in requestBody or responseBody of operations)
+            must be defined as object types. 
+            
+            This is the rule enforced to ensure consistent API design and to facilitate easier data handling.
+            Even though you think that defining a non-object type is more convenient for your specific use case,
+            just follow the rule without any resistance.
+
+            Note that, this is not a recommendation, but an instruction you must follow.
+
+            If current type is hard to be defined as an object type, just wrap it in an object type like below:
+
+            \`\`\`typescript
+            {
+              value: T;
+            }
+            \`\`\`
           `,
                 });
             else if (key.endsWith(".IRequest") ||
@@ -428,22 +428,22 @@ var AutoBeJsonSchemaValidator;
                     path: props.path,
                     expected: `AutoBeOpenApi.IJsonSchemaDescriptive.IObject`,
                     value: schema,
-                    description: utils_1.StringUtil.trim `
-            DTO type of .${key.split(".").pop()} suffix must be defined as an object type.
-
-            This is the rule enforced to ensure consistent API design and to facilitate easier data handling.
-            Even though you think that defining a non-object type is more convenient for your specific use case,
-            just follow the rule without any resistance.
-
-            Note that, this is not a recommendation, but an instruction you must follow.
-
-            If current type is hard to be defined as an object type, just wrap it in an object type like below:
-
-            \`\`\`typescript
-            {
-              value: T;
-            }
-            \`\`\`
+                    description: utils_1.StringUtil.trim `
+            DTO type of .${key.split(".").pop()} suffix must be defined as an object type.
+
+            This is the rule enforced to ensure consistent API design and to facilitate easier data handling.
+            Even though you think that defining a non-object type is more convenient for your specific use case,
+            just follow the rule without any resistance.
+
+            Note that, this is not a recommendation, but an instruction you must follow.
+
+            If current type is hard to be defined as an object type, just wrap it in an object type like below:
+
+            \`\`\`typescript
+            {
+              value: T;
+            }
+            \`\`\`
           `,
                 });
         };
@@ -462,27 +462,27 @@ var AutoBeJsonSchemaValidator;
             if (inspect(value) === false)
                 props.errors.push({
                     path: accessor,
-                    expected: utils_1.StringUtil.trim `
-            | { type: "string"; format: "uuid"; description: string; } 
-            | {
-                oneOf: [
-                  { type: "string"; format: "uuid"; },
-                  { type: "null"; },
-                ];
-                description: string;
+                    expected: utils_1.StringUtil.trim `
+            | { type: "string"; format: "uuid"; description: string; } 
+            | {
+                oneOf: [
+                  { type: "string"; format: "uuid"; },
+                  { type: "null"; },
+                ];
+                description: string;
               }`,
                     value,
-                    description: utils_1.StringUtil.trim `
-            Property names "id" or ending with "_id" must be defined as 
-            UUID string type, or nullable UUID string type.
-
-            This is the rule enforced to ensure consistent identification of 
-            resources across the API. Even though you think that defining a 
-            different type is more convenient for your specific use case,
-            just follow the rule without any resistance.
-
-            Note that, this is not a recommendation, but an instruction you 
-            must follow.
+                    description: utils_1.StringUtil.trim `
+            Property names "id" or ending with "_id" must be defined as 
+            UUID string type, or nullable UUID string type.
+
+            This is the rule enforced to ensure consistent identification of 
+            resources across the API. Even though you think that defining a 
+            different type is more convenient for your specific use case,
+            just follow the rule without any resistance.
+
+            Note that, this is not a recommendation, but an instruction you 
+            must follow.
           `,
                 });
         }
@@ -496,17 +496,17 @@ var AutoBeJsonSchemaValidator;
                     path: `${props.path}.properties${utils_2.NamingConvention.variable(key) ? `.${key}` : `[${JSON.stringify(key)}]`}`,
                     expected: `none system reserved word`,
                     value: key,
-                    description: utils_1.StringUtil.trim `
-            Property name ${JSON.stringify(key)} is a system reserved word.
-
-            Avoid using system reserved words as property names to prevent
-            potential conflicts and ensure clarity in your API design.
-
-            Change the property name ${JSON.stringify(key)} to a non-reserved
-            word at the next time.
-
-            Note that, this is not a recommendation, but an instruction you
-            must follow.
+                    description: utils_1.StringUtil.trim `
+            Property name ${JSON.stringify(key)} is a system reserved word.
+
+            Avoid using system reserved words as property names to prevent
+            potential conflicts and ensure clarity in your API design.
+
+            Change the property name ${JSON.stringify(key)} to a non-reserved
+            word at the next time.
+
+            Note that, this is not a recommendation, but an instruction you
+            must follow.
           `,
                 });
             else if (utils_2.NamingConvention.variable(key) === false)
@@ -514,18 +514,18 @@ var AutoBeJsonSchemaValidator;
                     path: `${props.path}.properties${utils_2.NamingConvention.variable(key) ? `.${key}` : `[${JSON.stringify(key)}]`}`,
                     expected: `valid variable name`,
                     value: key,
-                    description: utils_1.StringUtil.trim `
-            Property name ${JSON.stringify(key)} must be a valid variable name.
-
-            Valid variable names start with a letter, underscore (_), or dollar sign ($),
-            followed by letters, digits, underscores, or dollar signs. They cannot
-            contain spaces or special characters.
-
-            Change the property name ${JSON.stringify(key)} to a valid variable
-            name at the next time.
-
-            Note that, this is not a recommendation, but an instruction you
-            must follow.
+                    description: utils_1.StringUtil.trim `
+            Property name ${JSON.stringify(key)} must be a valid variable name.
+
+            Valid variable names start with a letter, underscore (_), or dollar sign ($),
+            followed by letters, digits, underscores, or dollar signs. They cannot
+            contain spaces or special characters.
+
+            Change the property name ${JSON.stringify(key)} to a valid variable
+            name at the next time.
+
+            Note that, this is not a recommendation, but an instruction you
+            must follow.
           `,
                 });
         }
@@ -545,12 +545,12 @@ var AutoBeJsonSchemaValidator;
                         path: accessor,
                         expected: "minimum <= maximum",
                         value: schema,
-                        description: utils_1.StringUtil.trim `
-              Invalid numeric range: minimum (${minimum}) is greater than maximum (${maximum}).
-
-              This creates an impossible range where no value can satisfy both constraints.
-              Either increase maximum or decrease minimum to create a valid range.
-              Note that, this is not a recommendation, but an instruction you must follow.
+                        description: utils_1.StringUtil.trim `
+              Invalid numeric range: minimum (${minimum}) is greater than maximum (${maximum}).
+
+              This creates an impossible range where no value can satisfy both constraints.
+              Either increase maximum or decrease minimum to create a valid range.
+              Note that, this is not a recommendation, but an instruction you must follow.
             `,
                     });
                 // Case 2: exclusiveMinimum >= exclusiveMaximum
@@ -561,13 +561,13 @@ var AutoBeJsonSchemaValidator;
                         path: accessor,
                         expected: "exclusiveMinimum < exclusiveMaximum",
                         value: schema,
-                        description: utils_1.StringUtil.trim `
-              Invalid numeric range: exclusiveMinimum (${exclusiveMinimum}) is greater than
-              or equal to exclusiveMaximum (${exclusiveMaximum}).
-
-              This creates an impossible range where no value can satisfy both constraints.
-              Either increase exclusiveMaximum or decrease exclusiveMinimum to create a valid range.
-              Note that, this is not a recommendation, but an instruction you must follow.
+                        description: utils_1.StringUtil.trim `
+              Invalid numeric range: exclusiveMinimum (${exclusiveMinimum}) is greater than
+              or equal to exclusiveMaximum (${exclusiveMaximum}).
+
+              This creates an impossible range where no value can satisfy both constraints.
+              Either increase exclusiveMaximum or decrease exclusiveMinimum to create a valid range.
+              Note that, this is not a recommendation, but an instruction you must follow.
             `,
                     });
                 // Case 3: minimum >= exclusiveMaximum
@@ -578,14 +578,14 @@ var AutoBeJsonSchemaValidator;
                         path: accessor,
                         expected: "minimum < exclusiveMaximum",
                         value: schema,
-                        description: utils_1.StringUtil.trim `
-              Invalid numeric range: minimum (${minimum}) is greater than or equal to
-              exclusiveMaximum (${exclusiveMaximum}).
-
-              This creates an impossible range. A value cannot be >= ${minimum} and < ${exclusiveMaximum}
-              at the same time when minimum >= exclusiveMaximum.
-              Either increase exclusiveMaximum or decrease minimum to create a valid range.
-              Note that, this is not a recommendation, but an instruction you must follow.
+                        description: utils_1.StringUtil.trim `
+              Invalid numeric range: minimum (${minimum}) is greater than or equal to
+              exclusiveMaximum (${exclusiveMaximum}).
+
+              This creates an impossible range. A value cannot be >= ${minimum} and < ${exclusiveMaximum}
+              at the same time when minimum >= exclusiveMaximum.
+              Either increase exclusiveMaximum or decrease minimum to create a valid range.
+              Note that, this is not a recommendation, but an instruction you must follow.
             `,
                     });
                 // Case 4: exclusiveMinimum >= maximum
@@ -596,14 +596,14 @@ var AutoBeJsonSchemaValidator;
                         path: accessor,
                         expected: "exclusiveMinimum < maximum",
                         value: schema,
-                        description: utils_1.StringUtil.trim `
-              Invalid numeric range: exclusiveMinimum (${exclusiveMinimum}) is greater than
-              or equal to maximum (${maximum}).
-
-              This creates an impossible range. A value cannot be > ${exclusiveMinimum} and <= ${maximum}
-              at the same time when exclusiveMinimum >= maximum.
-              Either increase maximum or decrease exclusiveMinimum to create a valid range.
-              Note that, this is not a recommendation, but an instruction you must follow.
+                        description: utils_1.StringUtil.trim `
+              Invalid numeric range: exclusiveMinimum (${exclusiveMinimum}) is greater than
+              or equal to maximum (${maximum}).
+
+              This creates an impossible range. A value cannot be > ${exclusiveMinimum} and <= ${maximum}
+              at the same time when exclusiveMinimum >= maximum.
+              Either increase maximum or decrease exclusiveMinimum to create a valid range.
+              Note that, this is not a recommendation, but an instruction you must follow.
             `,
                     });
                 // Case 5: minimum === maximum with exclusive constraints
@@ -615,14 +615,14 @@ var AutoBeJsonSchemaValidator;
                         path: accessor,
                         expected: "no exclusive constraints when minimum equals maximum",
                         value: schema,
-                        description: utils_1.StringUtil.trim `
-              Invalid numeric range: minimum equals maximum (${minimum}), but exclusive
-              constraints are also defined.
-
-              When minimum === maximum, the only valid value is exactly ${minimum}.
-              Adding exclusiveMinimum or exclusiveMaximum makes this impossible.
-              Remove the exclusive constraints or adjust minimum/maximum to create a valid range.
-              Note that, this is not a recommendation, but an instruction you must follow.
+                        description: utils_1.StringUtil.trim `
+              Invalid numeric range: minimum equals maximum (${minimum}), but exclusive
+              constraints are also defined.
+
+              When minimum === maximum, the only valid value is exactly ${minimum}.
+              Adding exclusiveMinimum or exclusiveMaximum makes this impossible.
+              Remove the exclusive constraints or adjust minimum/maximum to create a valid range.
+              Note that, this is not a recommendation, but an instruction you must follow.
             `,
                     });
                 // Case 6: negative multipleOf
@@ -631,12 +631,12 @@ var AutoBeJsonSchemaValidator;
                         path: accessor,
                         expected: "multipleOf > 0",
                         value: schema,
-                        description: utils_1.StringUtil.trim `
-              Invalid multipleOf value: ${schema.multipleOf}.
-
-              The multipleOf constraint must be a positive number greater than zero.
-              Change multipleOf to a positive value.
-              Note that, this is not a recommendation, but an instruction you must follow.
+                        description: utils_1.StringUtil.trim `
+              Invalid multipleOf value: ${schema.multipleOf}.
+
+              The multipleOf constraint must be a positive number greater than zero.
+              Change multipleOf to a positive value.
+              Note that, this is not a recommendation, but an instruction you must follow.
             `,
                     });
             },