oneentry 1.0.168 → 1.0.170

package/changelog.md

@@ -1,5 +1,29 @@
 # SDK Change Log
 
+## v.1.0.170
+
+### What's Changed
+
+- **`IAttributeValidators` named four validators of the eighteen the platform accepts.** The interface gave a shape to `requiredValidator`, `stringInspectionValidator`, `emailInspectionValidator` and `defaultValueValidator`, and closed with `[key: string]: unknown`; its JSDoc said only that the set is extensible. A developer reading the types learned that a required flag, a length constraint, an e-mail toggle and a default value exist, and did not learn that a **regular expression**, an **input mask**, a **whitespace trim** and **date bounds** exist — fourteen capabilities absent from the model of the platform, which on one pilot reached three client-facing documents as the sentence "a field has exactly four validators; there are no regular expressions and no phone check". All eighteen names are now declared with the shape the platform stores: `requiredValidator`, `trimValidator`, `stringInspectionValidator`, `urlInspectionValidator`, `emailInspectionValidator`, `checkForNumberValidator`, `roundingNumberValidator`, `booleanValidator`, `comparisonValidator`, `regExpValidator`, `fieldMaskValidator`, `checkForAGivenList`, `defaultValueValidator`, `sizeInPixelsValidator`, `checkingFilesValidator`, `minMaxDateValidator`, `valueValidator`, `checkForLettersValidator` (CMS-983).
+
+- **A misspelt validator name is a compile error instead of a `400`.** The index signature `[key: string]: unknown` made the gap silent in the other direction too: `emailValidator` typechecked and the platform refused the write at run time with `schema contains unknown validator name(s)`. The signature is gone, so an unknown name is caught where it is written. Code that still needs a name the SDK does not know can cast at that one place.
+
+- **Shapes follow what the platform executes, not what reads well.** `regExpValidator` takes `{ patternValue, invert, flags }` and not `{ regExp }`, `fieldMaskValidator` takes `{ maskValue }`, `checkForAGivenList` carries no `Validator` suffix, and `minMaxDateValidator` stores `minDateTimeValue` / `maxDateTimeValue`. The toggles — `requiredValidator`, `trimValidator`, `urlInspectionValidator`, `emailInspectionValidator` — are typed `object | boolean`, because both forms are in live data: an e-mail check is stored as the boolean `true` on seven fields of the stands checked and as an object on one. Every validator may also carry `customErrorText`, which is now in the type. `valueValidator` is kept with the same shape as `defaultValueValidator`: it is the panel's own name for that control, and the API stores it.
+
+- **The attribute JSDoc in `base/utils.ts` named `regexValidator`,** which does not exist. It points at `IAttributeValidators` for the full list instead.
+
+Types and documentation only; the wire format did not change.
+
+## v.1.0.169
+
+### What's Fixed
+
+- **A response that is not JSON came back as a parser message, and on the error branch as nothing at all.** The platform has been seen answering `200 OK` with `content-type: text/html` and its own admin page as the body — every content endpoint of a project at once, for minutes, a single request enough to reproduce it (CMS-957). A successful status carrying someone else's body cannot be told apart from a real answer by status alone, and all the caller got was `SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON`: a sentence about the SDK's own parsing rather than about what arrived. Read as "this record does not exist", it made a static build of a demo shop bake `404` into 8 of 54 product pages while every one of those products was live. The same body behind a failing status was worse: `_parseJson` swallowed it and returned `{}`, which carries no `statusCode` and therefore does not read as an error at all, so a `502` came back looking like an empty success. A body that is not JSON is now described — `Expected JSON from the platform, received text/html (HTTP 200): <!DOCTYPE html>…` — with `statusCode: 0` on a successful status, the same "no usable answer" contract as a dropped connection, and the status the server really sent when it failed. Token refresh reads its body through the same helper instead of `response.json()`, so an HTML answer there fails the refresh rather than throwing a raw parse error out of the request that triggered it.
+
+### Tests
+
+- **`src/base/tests/nonjson.spec.ts` pins the five outcomes** with a stubbed `fetch`, no stand required: HTML behind a `200`, HTML behind a `502`, a normal JSON answer, an empty body, and an error the platform itself sent.
+
 ## v.1.0.168
 
 ### What's Fixed

package/dist/attribute-sets/attributeSetsInterfaces.d.ts

@@ -189,28 +189,130 @@ interface IAttributeSchemaItem {
 }
 /**
  * @interface IAttributeValidators
- * @property {object} [requiredValidator] - Marks the field as required. Shape: `{ strict: boolean }`. Example: `{ strict: true }`.
- * @property {object} [stringInspectionValidator] - Length constraints for string fields. Shape: `{ stringMin: number; stringMax: number; stringLength: number }`.
- * @property {boolean} [emailInspectionValidator] - Toggle for email-format validation.
- * @property {object} [defaultValueValidator] - Default value configuration with optional custom error text. Shape: `{ customErrorText?: string; fieldDefaultValue?: unknown; fieldDefaultValue2?: unknown }`.
- * @description Map of validators applied to an attribute or form field. Set is extensible — additional validator types may be added by the API.
+ * @property {object | boolean} [requiredValidator] - Field must be filled in. Shape: `{ strict: boolean }`. Example: `{ strict: true }`.
+ * @property {object | boolean} [trimValidator] - Leading and trailing whitespace is stripped from the value. Stored as an empty object when the toggle is on. Example: `{}`.
+ * @property {object} [stringInspectionValidator] - Length constraints for string fields. Example: `{ stringLength: 0, stringMin: 2, stringMax: 60 }`.
+ * @property {object | boolean} [urlInspectionValidator] - Value must look like a URL. Stored either as `true` or as an object. Example: `true`.
+ * @property {object | boolean} [emailInspectionValidator] - Value must look like an e-mail address. Stored either as `true` or as an object. Example: `true`.
+ * @property {object} [checkForNumberValidator] - Value must be a number, optionally an integer within bounds. `0` disables a bound. Example: `{ integerOnly: true, minValue: 1, maxValue: 10 }`.
+ * @property {object} [roundingNumberValidator] - Rounds the number before storing it. Example: `{ integerOnly: false, numberOfDecimals: 2, direction: 'round' }`.
+ * @property {object} [booleanValidator] - Value must equal one of the two declared values. Example: `{ trueValue: 1, falseValue: 0 }`.
+ * @property {object} [comparisonValidator] - Compares the value with another attribute or with a constant. Example: `{ compareAttribute: 'notChoosed', compareValue: '10', type: 'number', operator: 'equality' }`.
+ * @property {object} [regExpValidator] - Value must match a regular expression; `invert` refuses matches instead. Example: `{ patternValue: '^[0-9]{5}$', invert: false, flags: ['i'] }`.
+ * @property {object} [fieldMaskValidator] - Value must match an input mask (`9` digit, `A` upper letter, `a` lower letter, `*` any, `$` one of `()+-`). Example: `{ maskValue: '+9 (999) 999-99-99' }`.
+ * @property {object} [checkForAGivenList] - Value must be in the list, or outside it when `notValue` is true. Example: `{ rangeValue: ['red', 'green'], notValue: false }`.
+ * @property {object} [defaultValueValidator] - Value substituted when the field is left empty. Example: `{ fieldDefaultValue: 'USD' }`.
+ * @property {object} [sizeInPixelsValidator] - Image bounds in pixels; executed by the admin panel. Example: `{ maxX: 1920, maxY: 1080 }`.
+ * @property {object} [checkingFilesValidator] - File size bounds and allowed extensions; executed by the admin panel. Example: `{ minValue: 0, maxValue: 5, minUnits: 'kb', maxUnits: 'mb', extensions: ['pdf'] }`.
+ * @property {object} [minMaxDateValidator] - Date bounds; executed by the admin panel. Example: `{ minDateTimeValue: '2026-01-01', maxDateTimeValue: '2026-12-31' }`.
+ * @property {object} [valueValidator] - The panel's "default value" control; it writes `defaultValueValidator`, and this name is kept because the API accepts and stores it. Example: `{ fieldDefaultValue: 'USD' }`.
+ * @property {object} [checkForLettersValidator] - Letters-only check by pattern; executed by the admin panel. Example: `{ patternValue: '^[A-Za-z ]+$' }`.
+ * @description Map of validators applied to an attribute or form field, keyed by validator name.
+ *
+ * These eighteen names are the full set the API accepts in
+ * `attributes_sets.schema.<attribute>.validators.<langCode>`; any other name is refused
+ * with `400`. The first thirteen are executed by the platform on write, the last five are
+ * stored as given and executed by the admin panel.
+ *
+ * Every validator may also carry `customErrorText` — the message shown instead of the
+ * default one when the value is refused.
  */
 interface IAttributeValidators {
     requiredValidator?: {
-        strict: boolean;
-    };
+        strict?: boolean;
+        customErrorText?: string;
+    } | boolean;
+    trimValidator?: {
+        strict?: boolean;
+        customErrorText?: string;
+    } | boolean;
     stringInspectionValidator?: {
-        stringMin: number;
-        stringMax: number;
-        stringLength: number;
+        stringMin?: number;
+        stringMax?: number;
+        stringLength?: number;
+        customErrorText?: string;
+    };
+    urlInspectionValidator?: {
+        strict?: boolean;
+        customErrorText?: string;
+    } | boolean;
+    emailInspectionValidator?: {
+        strict?: boolean;
+        customErrorText?: string;
+    } | boolean;
+    checkForNumberValidator?: {
+        integerOnly?: boolean;
+        minValue?: number;
+        maxValue?: number;
+        customErrorText?: string;
+    };
+    roundingNumberValidator?: {
+        integerOnly?: boolean;
+        numberOfDecimals?: number;
+        direction?: 'round' | 'up' | 'down' | 'truncate';
+        customErrorText?: string;
+    };
+    booleanValidator?: {
+        trueValue?: unknown;
+        falseValue?: unknown;
+        customErrorText?: string;
+    };
+    comparisonValidator?: {
+        compareAttribute?: string;
+        compareValue?: string;
+        compareValue2?: string;
+        type?: string;
+        operator?: string;
+        customErrorText?: string;
+    };
+    regExpValidator?: {
+        patternValue?: string;
+        invert?: boolean;
+        flags?: string[];
+        customErrorText?: string;
+    };
+    fieldMaskValidator?: {
+        maskValue?: string;
+        customErrorText?: string;
+    };
+    checkForAGivenList?: {
+        rangeValue?: unknown[];
+        rangeValue2?: unknown[];
+        notValue?: boolean;
+        customErrorText?: string;
     };
-    emailInspectionValidator?: boolean;
     defaultValueValidator?: {
+        fieldDefaultValue?: unknown;
+        fieldDefaultValue2?: unknown;
+        customErrorText?: string;
+    };
+    sizeInPixelsValidator?: {
+        maxX?: number;
+        maxY?: number;
         customErrorText?: string;
+    };
+    checkingFilesValidator?: {
+        minValue?: number;
+        maxValue?: number;
+        minUnits?: 'kb' | 'mb';
+        maxUnits?: 'kb' | 'mb';
+        extensions?: string[];
+        customErrorText?: string;
+    };
+    minMaxDateValidator?: {
+        minDateTimeValue?: string;
+        maxDateTimeValue?: string;
+        customErrorText?: string;
+    };
+    valueValidator?: {
         fieldDefaultValue?: unknown;
         fieldDefaultValue2?: unknown;
+        customErrorText?: string;
+    };
+    checkForLettersValidator?: {
+        patternValue?: string;
+        customErrorText?: string;
     };
-    [key: string]: unknown;
 }
 /**
  * Represents an attribute set entity.

package/dist/base/asyncModules.d.ts

@@ -103,13 +103,19 @@ export default abstract class AsyncModules extends SyncModules {
      */
     private makeOptions;
     /**
-     * Reads a response body as JSON, tolerating an empty body.
+     * Reads an error response body as JSON, tolerating an empty body.
      *
      * `Response.json()` throws on an empty body (e.g. 204 or an empty error
      * payload); this helper mirrors the OK-path guard (`text ? JSON.parse : {}`)
      * so both the success and the error branches handle empty bodies the same way.
+     *
+     * A body that is present but is not JSON — a gateway's HTML page in front of a
+     * 502, the platform's own admin page (CMS-957) — used to collapse into `{}`,
+     * which carries no `statusCode` and therefore does not read as an error at all:
+     * a failed request came back looking like an empty success. It is described
+     * instead, keeping the status the server actually sent.
      * @param {Response} response - The fetch Response to read.
-     * @returns {Promise<unknown>} Parsed JSON, or an empty object when the body is empty/unparsable.
+     * @returns {Promise<unknown>} Parsed JSON, `{}` for an empty body, or a described error for a body that is not JSON.
      */
     private _parseJson;
     /**
@@ -120,6 +126,26 @@ export default abstract class AsyncModules extends SyncModules {
      * @description Define an asynchronous method 'browserResponse' that takes a path and options as parameters
      */
     private browserResponse;
+    /**
+     * Describes a response whose body is not the JSON the API is supposed to send.
+     *
+     * The platform has been seen answering `200 OK` with `content-type: text/html`
+     * and the admin page as the body — every content endpoint at once, for minutes
+     * (CMS-957). A successful status carrying someone else's body is indistinguishable
+     * from a real answer by status alone, and the only symptom used to be
+     * `SyntaxError: Unexpected token '<'` from the JSON parser: a message about the
+     * SDK's own parsing rather than about what the platform did. Callers read that as
+     * "this record does not exist" and a static build baked 404s over live products.
+     *
+     * The returned error names the received content type, the HTTP status and the
+     * first characters of the body, so a log line says what arrived instead of JSON.
+     * `statusCode` stays `0` — the request produced no usable answer, the same
+     * contract as a dropped connection, and a value no HTTP answer uses.
+     * @param {Response} response - The response whose body could not be parsed.
+     * @param {string} text - The raw body as read.
+     * @returns {IError} The error in the shape the SDK returns for platform errors.
+     */
+    private _nonJsonError;
     /**
      * Turns whatever was thrown into the error shape the SDK already returns.
      *

package/dist/base/asyncModules.js

@@ -239,8 +239,14 @@ class AsyncModules extends syncModules_1.default {
         });
         // Check if the response status is OK (status code 200-299)
         if (response.ok) {
-            // Parse the response body as JSON and store the result
-            const result = await response.json();
+            // Parsed through the shared helper rather than `response.json()`: a `200` whose body is
+            // not JSON (CMS-957) threw a raw SyntaxError out of the refresh and took the request that
+            // triggered it with it. A body without tokens is a failed refresh, reported as such.
+            const result = await this._parseJson(response);
+            if (typeof (result === null || result === void 0 ? void 0 : result.refreshToken) !== 'string' ||
+                typeof (result === null || result === void 0 ? void 0 : result.accessToken) !== 'string') {
+                return false;
+            }
             // Update the state's refreshToken and accessToken with the new tokens from the response
             this.state.refreshToken = result.refreshToken;
             this.state.accessToken = result.accessToken;
@@ -313,22 +319,37 @@ class AsyncModules extends syncModules_1.default {
         return options;
     }
     /**
-     * Reads a response body as JSON, tolerating an empty body.
+     * Reads an error response body as JSON, tolerating an empty body.
      *
      * `Response.json()` throws on an empty body (e.g. 204 or an empty error
      * payload); this helper mirrors the OK-path guard (`text ? JSON.parse : {}`)
      * so both the success and the error branches handle empty bodies the same way.
+     *
+     * A body that is present but is not JSON — a gateway's HTML page in front of a
+     * 502, the platform's own admin page (CMS-957) — used to collapse into `{}`,
+     * which carries no `statusCode` and therefore does not read as an error at all:
+     * a failed request came back looking like an empty success. It is described
+     * instead, keeping the status the server actually sent.
      * @param {Response} response - The fetch Response to read.
-     * @returns {Promise<unknown>} Parsed JSON, or an empty object when the body is empty/unparsable.
+     * @returns {Promise<unknown>} Parsed JSON, `{}` for an empty body, or a described error for a body that is not JSON.
      */
     async _parseJson(response) {
+        let text;
         try {
-            const text = await response.text();
-            return text ? JSON.parse(text) : {};
+            text = await response.text();
         }
         catch {
             return {};
         }
+        if (!text) {
+            return {};
+        }
+        try {
+            return JSON.parse(text);
+        }
+        catch {
+            return this._nonJsonError(response, text);
+        }
     }
     /**
      * Handles responses from the browser's fetch API.
@@ -386,10 +407,18 @@ class AsyncModules extends syncModules_1.default {
             // Check if the response status is OK (status code 200-299)
             if (response.ok) {
                 // Read the body as text; if it is empty return an empty object,
-                // otherwise parse it as JSON. A parse failure propagates to the
-                // catch below and is handled according to isShell.
+                // otherwise parse it as JSON. A body that is not JSON is turned into a
+                // described error by `_nonJsonError` and handled according to isShell.
                 const text = await response.text();
-                return (text ? JSON.parse(text) : {});
+                if (!text) {
+                    return {};
+                }
+                try {
+                    return JSON.parse(text);
+                }
+                catch {
+                    throw this._nonJsonError(response, text);
+                }
             }
             // Handle non-OK responses (applies to the first response and to a failed retry).
             const status = response.status;
@@ -417,6 +446,40 @@ class AsyncModules extends syncModules_1.default {
             }
         }
     }
+    /**
+     * Describes a response whose body is not the JSON the API is supposed to send.
+     *
+     * The platform has been seen answering `200 OK` with `content-type: text/html`
+     * and the admin page as the body — every content endpoint at once, for minutes
+     * (CMS-957). A successful status carrying someone else's body is indistinguishable
+     * from a real answer by status alone, and the only symptom used to be
+     * `SyntaxError: Unexpected token '<'` from the JSON parser: a message about the
+     * SDK's own parsing rather than about what the platform did. Callers read that as
+     * "this record does not exist" and a static build baked 404s over live products.
+     *
+     * The returned error names the received content type, the HTTP status and the
+     * first characters of the body, so a log line says what arrived instead of JSON.
+     * `statusCode` stays `0` — the request produced no usable answer, the same
+     * contract as a dropped connection, and a value no HTTP answer uses.
+     * @param {Response} response - The response whose body could not be parsed.
+     * @param {string} text - The raw body as read.
+     * @returns {IError} The error in the shape the SDK returns for platform errors.
+     */
+    _nonJsonError(response, text) {
+        var _a, _b, _c;
+        const contentType = (_c = (_b = (_a = response.headers) === null || _a === void 0 ? void 0 : _a.get) === null || _b === void 0 ? void 0 : _b.call(_a, 'content-type')) !== null && _c !== void 0 ? _c : 'unknown';
+        const excerpt = text.trim().slice(0, 120).replace(/\s+/g, ' ');
+        return {
+            // A successful status carrying a non-JSON body produced no usable answer, the same
+            // contract as a dropped connection. A failing one already says something true about
+            // the request, so that status is kept.
+            statusCode: response.ok ? 0 : response.status,
+            message: `Expected JSON from the platform, received ${contentType} ` +
+                `(HTTP ${response.status}): ${excerpt}`,
+            pageData: null,
+            timestamp: new Date().toISOString(),
+        };
+    }
     /**
      * Turns whatever was thrown into the error shape the SDK already returns.
      *

package/dist/base/utils.d.ts

@@ -96,7 +96,7 @@ interface IConfig {
  * @property {boolean} isVisible - Whether the attribute is exposed in the public API/UI. Example: true.
  * @property {string} type - Attribute data type (e.g. "string", "integer", "list", "file", "image").
  * @property {Record<string, unknown>} [settings] - Type-specific configuration (e.g. min/max for numbers, accepted MIME types for files). Optional.
- * @property {Record<string, unknown>} validators - Validation rules applied to the attribute value (e.g. `requiredValidator`, `regexValidator`). Example: { "requiredValidator": { "strict": true } }.
+ * @property {Record<string, unknown>} validators - Validation rules applied to the attribute value, keyed by validator name (e.g. `requiredValidator`, `regExpValidator`); the full set of names is listed on `IAttributeValidators`. Example: { "requiredValidator": { "strict": true } }.
  * @property {Record<string, IAttributes>} [additionalFields] - Nested sub-attributes attached to this attribute, keyed by marker. Optional.
  * @property {boolean} [isIcon] - Block/preview attribute flag — whether the field is treated as an icon. Optional.
  * @property {boolean} [isProductPreview] - Block/preview attribute flag — whether the field is shown in product preview. Optional.

package/esm/attribute-sets/attributeSetsInterfaces.d.ts

@@ -189,28 +189,130 @@ interface IAttributeSchemaItem {
 }
 /**
  * @interface IAttributeValidators
- * @property {object} [requiredValidator] - Marks the field as required. Shape: `{ strict: boolean }`. Example: `{ strict: true }`.
- * @property {object} [stringInspectionValidator] - Length constraints for string fields. Shape: `{ stringMin: number; stringMax: number; stringLength: number }`.
- * @property {boolean} [emailInspectionValidator] - Toggle for email-format validation.
- * @property {object} [defaultValueValidator] - Default value configuration with optional custom error text. Shape: `{ customErrorText?: string; fieldDefaultValue?: unknown; fieldDefaultValue2?: unknown }`.
- * @description Map of validators applied to an attribute or form field. Set is extensible — additional validator types may be added by the API.
+ * @property {object | boolean} [requiredValidator] - Field must be filled in. Shape: `{ strict: boolean }`. Example: `{ strict: true }`.
+ * @property {object | boolean} [trimValidator] - Leading and trailing whitespace is stripped from the value. Stored as an empty object when the toggle is on. Example: `{}`.
+ * @property {object} [stringInspectionValidator] - Length constraints for string fields. Example: `{ stringLength: 0, stringMin: 2, stringMax: 60 }`.
+ * @property {object | boolean} [urlInspectionValidator] - Value must look like a URL. Stored either as `true` or as an object. Example: `true`.
+ * @property {object | boolean} [emailInspectionValidator] - Value must look like an e-mail address. Stored either as `true` or as an object. Example: `true`.
+ * @property {object} [checkForNumberValidator] - Value must be a number, optionally an integer within bounds. `0` disables a bound. Example: `{ integerOnly: true, minValue: 1, maxValue: 10 }`.
+ * @property {object} [roundingNumberValidator] - Rounds the number before storing it. Example: `{ integerOnly: false, numberOfDecimals: 2, direction: 'round' }`.
+ * @property {object} [booleanValidator] - Value must equal one of the two declared values. Example: `{ trueValue: 1, falseValue: 0 }`.
+ * @property {object} [comparisonValidator] - Compares the value with another attribute or with a constant. Example: `{ compareAttribute: 'notChoosed', compareValue: '10', type: 'number', operator: 'equality' }`.
+ * @property {object} [regExpValidator] - Value must match a regular expression; `invert` refuses matches instead. Example: `{ patternValue: '^[0-9]{5}$', invert: false, flags: ['i'] }`.
+ * @property {object} [fieldMaskValidator] - Value must match an input mask (`9` digit, `A` upper letter, `a` lower letter, `*` any, `$` one of `()+-`). Example: `{ maskValue: '+9 (999) 999-99-99' }`.
+ * @property {object} [checkForAGivenList] - Value must be in the list, or outside it when `notValue` is true. Example: `{ rangeValue: ['red', 'green'], notValue: false }`.
+ * @property {object} [defaultValueValidator] - Value substituted when the field is left empty. Example: `{ fieldDefaultValue: 'USD' }`.
+ * @property {object} [sizeInPixelsValidator] - Image bounds in pixels; executed by the admin panel. Example: `{ maxX: 1920, maxY: 1080 }`.
+ * @property {object} [checkingFilesValidator] - File size bounds and allowed extensions; executed by the admin panel. Example: `{ minValue: 0, maxValue: 5, minUnits: 'kb', maxUnits: 'mb', extensions: ['pdf'] }`.
+ * @property {object} [minMaxDateValidator] - Date bounds; executed by the admin panel. Example: `{ minDateTimeValue: '2026-01-01', maxDateTimeValue: '2026-12-31' }`.
+ * @property {object} [valueValidator] - The panel's "default value" control; it writes `defaultValueValidator`, and this name is kept because the API accepts and stores it. Example: `{ fieldDefaultValue: 'USD' }`.
+ * @property {object} [checkForLettersValidator] - Letters-only check by pattern; executed by the admin panel. Example: `{ patternValue: '^[A-Za-z ]+$' }`.
+ * @description Map of validators applied to an attribute or form field, keyed by validator name.
+ *
+ * These eighteen names are the full set the API accepts in
+ * `attributes_sets.schema.<attribute>.validators.<langCode>`; any other name is refused
+ * with `400`. The first thirteen are executed by the platform on write, the last five are
+ * stored as given and executed by the admin panel.
+ *
+ * Every validator may also carry `customErrorText` — the message shown instead of the
+ * default one when the value is refused.
  */
 interface IAttributeValidators {
     requiredValidator?: {
-        strict: boolean;
-    };
+        strict?: boolean;
+        customErrorText?: string;
+    } | boolean;
+    trimValidator?: {
+        strict?: boolean;
+        customErrorText?: string;
+    } | boolean;
     stringInspectionValidator?: {
-        stringMin: number;
-        stringMax: number;
-        stringLength: number;
+        stringMin?: number;
+        stringMax?: number;
+        stringLength?: number;
+        customErrorText?: string;
+    };
+    urlInspectionValidator?: {
+        strict?: boolean;
+        customErrorText?: string;
+    } | boolean;
+    emailInspectionValidator?: {
+        strict?: boolean;
+        customErrorText?: string;
+    } | boolean;
+    checkForNumberValidator?: {
+        integerOnly?: boolean;
+        minValue?: number;
+        maxValue?: number;
+        customErrorText?: string;
+    };
+    roundingNumberValidator?: {
+        integerOnly?: boolean;
+        numberOfDecimals?: number;
+        direction?: 'round' | 'up' | 'down' | 'truncate';
+        customErrorText?: string;
+    };
+    booleanValidator?: {
+        trueValue?: unknown;
+        falseValue?: unknown;
+        customErrorText?: string;
+    };
+    comparisonValidator?: {
+        compareAttribute?: string;
+        compareValue?: string;
+        compareValue2?: string;
+        type?: string;
+        operator?: string;
+        customErrorText?: string;
+    };
+    regExpValidator?: {
+        patternValue?: string;
+        invert?: boolean;
+        flags?: string[];
+        customErrorText?: string;
+    };
+    fieldMaskValidator?: {
+        maskValue?: string;
+        customErrorText?: string;
+    };
+    checkForAGivenList?: {
+        rangeValue?: unknown[];
+        rangeValue2?: unknown[];
+        notValue?: boolean;
+        customErrorText?: string;
     };
-    emailInspectionValidator?: boolean;
     defaultValueValidator?: {
+        fieldDefaultValue?: unknown;
+        fieldDefaultValue2?: unknown;
+        customErrorText?: string;
+    };
+    sizeInPixelsValidator?: {
+        maxX?: number;
+        maxY?: number;
         customErrorText?: string;
+    };
+    checkingFilesValidator?: {
+        minValue?: number;
+        maxValue?: number;
+        minUnits?: 'kb' | 'mb';
+        maxUnits?: 'kb' | 'mb';
+        extensions?: string[];
+        customErrorText?: string;
+    };
+    minMaxDateValidator?: {
+        minDateTimeValue?: string;
+        maxDateTimeValue?: string;
+        customErrorText?: string;
+    };
+    valueValidator?: {
         fieldDefaultValue?: unknown;
         fieldDefaultValue2?: unknown;
+        customErrorText?: string;
+    };
+    checkForLettersValidator?: {
+        patternValue?: string;
+        customErrorText?: string;
     };
-    [key: string]: unknown;
 }
 /**
  * Represents an attribute set entity.

package/esm/base/asyncModules.d.ts

@@ -103,13 +103,19 @@ export default abstract class AsyncModules extends SyncModules {
      */
     private makeOptions;
     /**
-     * Reads a response body as JSON, tolerating an empty body.
+     * Reads an error response body as JSON, tolerating an empty body.
      *
      * `Response.json()` throws on an empty body (e.g. 204 or an empty error
      * payload); this helper mirrors the OK-path guard (`text ? JSON.parse : {}`)
      * so both the success and the error branches handle empty bodies the same way.
+     *
+     * A body that is present but is not JSON — a gateway's HTML page in front of a
+     * 502, the platform's own admin page (CMS-957) — used to collapse into `{}`,
+     * which carries no `statusCode` and therefore does not read as an error at all:
+     * a failed request came back looking like an empty success. It is described
+     * instead, keeping the status the server actually sent.
      * @param {Response} response - The fetch Response to read.
-     * @returns {Promise<unknown>} Parsed JSON, or an empty object when the body is empty/unparsable.
+     * @returns {Promise<unknown>} Parsed JSON, `{}` for an empty body, or a described error for a body that is not JSON.
      */
     private _parseJson;
     /**
@@ -120,6 +126,26 @@ export default abstract class AsyncModules extends SyncModules {
      * @description Define an asynchronous method 'browserResponse' that takes a path and options as parameters
      */
     private browserResponse;
+    /**
+     * Describes a response whose body is not the JSON the API is supposed to send.
+     *
+     * The platform has been seen answering `200 OK` with `content-type: text/html`
+     * and the admin page as the body — every content endpoint at once, for minutes
+     * (CMS-957). A successful status carrying someone else's body is indistinguishable
+     * from a real answer by status alone, and the only symptom used to be
+     * `SyntaxError: Unexpected token '<'` from the JSON parser: a message about the
+     * SDK's own parsing rather than about what the platform did. Callers read that as
+     * "this record does not exist" and a static build baked 404s over live products.
+     *
+     * The returned error names the received content type, the HTTP status and the
+     * first characters of the body, so a log line says what arrived instead of JSON.
+     * `statusCode` stays `0` — the request produced no usable answer, the same
+     * contract as a dropped connection, and a value no HTTP answer uses.
+     * @param {Response} response - The response whose body could not be parsed.
+     * @param {string} text - The raw body as read.
+     * @returns {IError} The error in the shape the SDK returns for platform errors.
+     */
+    private _nonJsonError;
     /**
      * Turns whatever was thrown into the error shape the SDK already returns.
      *

package/esm/base/asyncModules.js

@@ -201,8 +201,14 @@ export default class AsyncModules extends SyncModules {
         });
         // Check if the response status is OK (status code 200-299)
         if (response.ok) {
-            // Parse the response body as JSON and store the result
-            const result = await response.json();
+            // Parsed through the shared helper rather than `response.json()`: a `200` whose body is
+            // not JSON (CMS-957) threw a raw SyntaxError out of the refresh and took the request that
+            // triggered it with it. A body without tokens is a failed refresh, reported as such.
+            const result = await this._parseJson(response);
+            if (typeof (result === null || result === void 0 ? void 0 : result.refreshToken) !== 'string' ||
+                typeof (result === null || result === void 0 ? void 0 : result.accessToken) !== 'string') {
+                return false;
+            }
             // Update the state's refreshToken and accessToken with the new tokens from the response
             this.state.refreshToken = result.refreshToken;
             this.state.accessToken = result.accessToken;
@@ -275,22 +281,37 @@ export default class AsyncModules extends SyncModules {
         return options;
     }
     /**
-     * Reads a response body as JSON, tolerating an empty body.
+     * Reads an error response body as JSON, tolerating an empty body.
      *
      * `Response.json()` throws on an empty body (e.g. 204 or an empty error
      * payload); this helper mirrors the OK-path guard (`text ? JSON.parse : {}`)
      * so both the success and the error branches handle empty bodies the same way.
+     *
+     * A body that is present but is not JSON — a gateway's HTML page in front of a
+     * 502, the platform's own admin page (CMS-957) — used to collapse into `{}`,
+     * which carries no `statusCode` and therefore does not read as an error at all:
+     * a failed request came back looking like an empty success. It is described
+     * instead, keeping the status the server actually sent.
      * @param {Response} response - The fetch Response to read.
-     * @returns {Promise<unknown>} Parsed JSON, or an empty object when the body is empty/unparsable.
+     * @returns {Promise<unknown>} Parsed JSON, `{}` for an empty body, or a described error for a body that is not JSON.
      */
     async _parseJson(response) {
+        let text;
         try {
-            const text = await response.text();
-            return text ? JSON.parse(text) : {};
+            text = await response.text();
         }
         catch {
             return {};
         }
+        if (!text) {
+            return {};
+        }
+        try {
+            return JSON.parse(text);
+        }
+        catch {
+            return this._nonJsonError(response, text);
+        }
     }
     /**
      * Handles responses from the browser's fetch API.
@@ -348,10 +369,18 @@ export default class AsyncModules extends SyncModules {
             // Check if the response status is OK (status code 200-299)
             if (response.ok) {
                 // Read the body as text; if it is empty return an empty object,
-                // otherwise parse it as JSON. A parse failure propagates to the
-                // catch below and is handled according to isShell.
+                // otherwise parse it as JSON. A body that is not JSON is turned into a
+                // described error by `_nonJsonError` and handled according to isShell.
                 const text = await response.text();
-                return (text ? JSON.parse(text) : {});
+                if (!text) {
+                    return {};
+                }
+                try {
+                    return JSON.parse(text);
+                }
+                catch {
+                    throw this._nonJsonError(response, text);
+                }
             }
             // Handle non-OK responses (applies to the first response and to a failed retry).
             const status = response.status;
@@ -379,6 +408,40 @@ export default class AsyncModules extends SyncModules {
             }
         }
     }
+    /**
+     * Describes a response whose body is not the JSON the API is supposed to send.
+     *
+     * The platform has been seen answering `200 OK` with `content-type: text/html`
+     * and the admin page as the body — every content endpoint at once, for minutes
+     * (CMS-957). A successful status carrying someone else's body is indistinguishable
+     * from a real answer by status alone, and the only symptom used to be
+     * `SyntaxError: Unexpected token '<'` from the JSON parser: a message about the
+     * SDK's own parsing rather than about what the platform did. Callers read that as
+     * "this record does not exist" and a static build baked 404s over live products.
+     *
+     * The returned error names the received content type, the HTTP status and the
+     * first characters of the body, so a log line says what arrived instead of JSON.
+     * `statusCode` stays `0` — the request produced no usable answer, the same
+     * contract as a dropped connection, and a value no HTTP answer uses.
+     * @param {Response} response - The response whose body could not be parsed.
+     * @param {string} text - The raw body as read.
+     * @returns {IError} The error in the shape the SDK returns for platform errors.
+     */
+    _nonJsonError(response, text) {
+        var _a, _b, _c;
+        const contentType = (_c = (_b = (_a = response.headers) === null || _a === void 0 ? void 0 : _a.get) === null || _b === void 0 ? void 0 : _b.call(_a, 'content-type')) !== null && _c !== void 0 ? _c : 'unknown';
+        const excerpt = text.trim().slice(0, 120).replace(/\s+/g, ' ');
+        return {
+            // A successful status carrying a non-JSON body produced no usable answer, the same
+            // contract as a dropped connection. A failing one already says something true about
+            // the request, so that status is kept.
+            statusCode: response.ok ? 0 : response.status,
+            message: `Expected JSON from the platform, received ${contentType} ` +
+                `(HTTP ${response.status}): ${excerpt}`,
+            pageData: null,
+            timestamp: new Date().toISOString(),
+        };
+    }
     /**
      * Turns whatever was thrown into the error shape the SDK already returns.
      *

package/esm/base/utils.d.ts

@@ -96,7 +96,7 @@ interface IConfig {
  * @property {boolean} isVisible - Whether the attribute is exposed in the public API/UI. Example: true.
  * @property {string} type - Attribute data type (e.g. "string", "integer", "list", "file", "image").
  * @property {Record<string, unknown>} [settings] - Type-specific configuration (e.g. min/max for numbers, accepted MIME types for files). Optional.
- * @property {Record<string, unknown>} validators - Validation rules applied to the attribute value (e.g. `requiredValidator`, `regexValidator`). Example: { "requiredValidator": { "strict": true } }.
+ * @property {Record<string, unknown>} validators - Validation rules applied to the attribute value, keyed by validator name (e.g. `requiredValidator`, `regExpValidator`); the full set of names is listed on `IAttributeValidators`. Example: { "requiredValidator": { "strict": true } }.
  * @property {Record<string, IAttributes>} [additionalFields] - Nested sub-attributes attached to this attribute, keyed by marker. Optional.
  * @property {boolean} [isIcon] - Block/preview attribute flag — whether the field is treated as an icon. Optional.
  * @property {boolean} [isProductPreview] - Block/preview attribute flag — whether the field is shown in product preview. Optional.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "oneentry",
-  "version": "1.0.168",
+  "version": "1.0.170",
   "description": "OneEntry NPM package",
   "main": "dist/index.js",
   "module": "esm/index.js",
@@ -48,7 +48,7 @@
   },
   "scripts": {
     "prepublishOnly": "node ../scripts/smoke-pack.js --files-only",
-    "postpublish": "node ../scripts/verify-published.js --named defineOneEntry --expect 1.0.168"
+    "postpublish": "node ../scripts/verify-published.js --named defineOneEntry --expect 1.0.170"
   },
   "sideEffects": false,
   "files": [