oneentry 1.0.164 → 1.0.165

package/changelog.md

@@ -1,5 +1,19 @@
 # SDK Change Log
 
+## v.1.0.165
+
+### What's New
+
+- **`AttributeType` now includes `json`.** The platform has a `json` attribute type, but the union listed every other type and not that one. Because `IAttributesSetsEntity.type` and `IAttributeSchemaItem.type` (and, through them, `IFormAttribute.type`) are typed by that union, a set containing a `json` field made `switch (field.type)` miss the branch and `field.type === 'json'` fail to compile with "This comparison appears to be unintentional" — the type the API actually sends was the one value the compiler refused to accept. Types only; the data has always come through.
+
+### What's Fixed
+
+- **FormData > `getFormsDataByMarker` no longer fails on an empty date filter.** `IFormsDataFilter` documents an empty string as "no bound" on `dateFrom`/`dateTo`, and that is how the endpoint used to read it — it now validates the pair as dates first and answers `400 dateFrom must be a valid date in format "YYYY-MM-DD" or "YYYY-MM-DD HH:MM:SS"`. So a filter built the documented way (`{ status: ['approved'], dateFrom: '', dateTo: '' }`) took down the whole request: no records, and an error about a bound the caller deliberately did not set. Every other field still treats `""` as "no filter", which made the failure look like anything but the date. The SDK now strips empty `dateFrom`/`dateTo` from the body before sending, restoring the documented meaning; a non-empty value the API cannot parse is still rejected, as it should be.
+
+### What's Deleted
+
+- **`textEditor` is gone from the text-attribute narrowing.** No such attribute type exists on the platform — rich text is `text` — but `IStringAttributeValue.type` declared `'string' | 'text' | 'textEditor'` and `isStringAttribute` checked for it. A value that never arrives cost nothing at runtime, yet it read as documentation: the union told everyone the CMS had a separate rich-text type, so `case 'textEditor'` branches were written and silently never taken, and someone looking for that type in the panel could not find it. `IStringAttributeValue.type` is now `'string' | 'text'`, the guard drops the third comparison, and the test case for it is removed.
+
 ## v.1.0.164
 
 ### What's Fixed

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

@@ -77,7 +77,7 @@ interface IListTitleExtended {
  * @type {AttributeType}
  * @description This type defines the possible values for attribute types used in the system.
  */
-type AttributeType = 'string' | 'text' | 'textWithHeader' | 'integer' | 'real' | 'float' | 'dateTime' | 'date' | 'time' | 'file' | 'image' | 'groupOfImages' | 'radioButton' | 'list' | 'button' | 'spam' | 'entity' | 'timeInterval';
+type AttributeType = 'string' | 'text' | 'textWithHeader' | 'integer' | 'real' | 'float' | 'dateTime' | 'date' | 'time' | 'file' | 'image' | 'groupOfImages' | 'radioButton' | 'list' | 'button' | 'spam' | 'entity' | 'timeInterval' | 'json';
 /**
  * Represents an attribute set entity.
  * @interface IAttributesSetsEntity

package/dist/base/attributes.d.ts

@@ -61,7 +61,7 @@ export declare function getAttributeFile(attr: IAttributeValue | undefined): IAt
 /**
  * Narrows an attribute value to a text attribute.
  * @param {IAttributeValue | undefined} attr - The attribute value to test.
- * @returns {boolean} True when the attribute is a `string`, `text` or `textEditor` carrying a string (or nothing).
+ * @returns {boolean} True when the attribute is a `string` or `text` carrying a string (or nothing).
  */
 export declare function isStringAttribute(attr: IAttributeValue | undefined): attr is IStringAttributeValue;
 /**

package/dist/base/attributes.js

@@ -101,13 +101,11 @@ function getAttributeFile(attr) {
 /**
  * Narrows an attribute value to a text attribute.
  * @param {IAttributeValue | undefined} attr - The attribute value to test.
- * @returns {boolean} True when the attribute is a `string`, `text` or `textEditor` carrying a string (or nothing).
+ * @returns {boolean} True when the attribute is a `string` or `text` carrying a string (or nothing).
  */
 function isStringAttribute(attr) {
     return (!!attr &&
-        (attr.type === 'string' ||
-            attr.type === 'text' ||
-            attr.type === 'textEditor') &&
+        (attr.type === 'string' || attr.type === 'text') &&
         (attr.value === null || typeof attr.value === 'string'));
 }
 /**

package/dist/base/utils.d.ts

@@ -325,12 +325,12 @@ interface IFileAttributeValue extends IAttributeValue {
 }
 /**
  * @interface IStringAttributeValue
- * @property {'string' | 'text' | 'textEditor'} type - Discriminant identifying the attribute as text-bearing.
+ * @property {'string' | 'text'} type - Discriminant identifying the attribute as text-bearing.
  * @property {string | null} value - The text; `null` when no value is set.
  * @description {@link IAttributeValue} narrowed to text attributes. Narrow to it with `isStringAttribute`.
  */
 interface IStringAttributeValue extends IAttributeValue {
-    type: 'string' | 'text' | 'textEditor';
+    type: 'string' | 'text';
     value: string | null;
 }
 /**

package/dist/forms-data/formsDataApi.d.ts

@@ -60,6 +60,21 @@ export default class FormsDataApi extends AsyncModules implements IFormsData {
      * @see {@link https://js-sdk.oneentry.cloud/docs/forms-data/postFormsData postFormsData} documentation.
      */
     postFormsData(body: IBodyPostFormData, langCode?: string): Promise<IPostFormResponse | IError>;
+    /**
+     * Drops the date bounds the endpoint refuses to parse.
+     *
+     * An empty string means "no filter" on every field of {@link IFormsDataFilter},
+     * and that is still how `entityIdentifier`, `userIdentifier` and an empty
+     * `status` array behave. The date pair is the exception: the endpoint now runs
+     * `dateFrom` / `dateTo` through a date validator before it builds the filter,
+     * so `dateFrom: ''` no longer means "no bound" — it fails the whole request
+     * with `400 dateFrom must be a valid date in format "YYYY-MM-DD"…` and takes
+     * the records down with it. An empty bound is therefore removed from the body
+     * rather than sent, which the API reads as "no bound", the documented meaning.
+     * @param {IFormsDataFilter} body - Filter body as passed by the caller.
+     * @returns {IFormsDataFilter} The same filter without empty date bounds.
+     */
+    private _stripEmptyDates;
     /**
      * Get one object of form data by marker.
      * @handleName getFormsDataByMarker
@@ -79,8 +94,8 @@ export default class FormsDataApi extends AsyncModules implements IFormsData {
      * @param {number} [body.parentId] - Identifier of the parent record, to fetch replies to one submission. Example: 10.
      * @param {string} [body.userIdentifier] - Text identifier of the sender. Example: "admin".
      * @param {FormDataStatus[]} [body.status] - Moderation statuses to keep: "sent", "moderation", "approved", "banned", "deleted". Must be an array; anything outside the set is rejected with `400 each value in status must be a valid enum value`. Example: ["approved"].
-     * @param {string} [body.dateFrom] - Lower bound of the submission date, `YYYY-MM-DD`. An unparsable value fails the request with a `500`. Example: "2025-01-01".
-     * @param {string} [body.dateTo] - Upper bound of the submission date, `YYYY-MM-DD`. Example: "2025-12-31".
+     * @param {string} [body.dateFrom] - Lower bound of the submission date, `YYYY-MM-DD`. An empty string means "no bound" — the SDK removes it from the body, because the endpoint answers `400 dateFrom must be a valid date in format "YYYY-MM-DD"` to one. An unparsable non-empty value still fails the request. Example: "2025-01-01".
+     * @param {string} [body.dateTo] - Upper bound of the submission date, `YYYY-MM-DD`. An empty string means "no bound", handled like `dateFrom`. Example: "2025-12-31".
      * @param {number} [isExtended] - Flag for getting additional fields. Example: 1.
      * @param {string} [langCode] - Language code. Default: "en_US".
      * @param {number} [offset] - Parameter for pagination. Default: 0.
@@ -90,6 +105,8 @@ export default class FormsDataApi extends AsyncModules implements IFormsData {
      * @description Each record's `formData` comes back **already unwrapped from its locale**. The API sends `formData: { "en_US": [ … ] }`; the SDK normalizes the response and hands over the array for `langCode`, so read `record.formData` — `record.formData[langCode]` is `undefined` and yields an empty list with no error. This holds for both values of `isExtended`.
      *
      * The filter body is typed for a reason: the API silently ignores a field it does not know, so a misspelled `statuses` returns every record — unmoderated ones included — and the code looks like it works.
+     *
+     * Empty `dateFrom` / `dateTo` are stripped from the body before it is sent: the endpoint validates the pair as dates and rejects an empty string with a `400`, while every other field still treats "" as "no filter".
      * @see {@link https://js-sdk.oneentry.cloud/docs/forms-data/getFormsDataByMarker getFormsDataByMarker} documentation.
      */
     getFormsDataByMarker(marker: string, formModuleConfigId: number, body?: IFormsDataFilter, isExtended?: number, langCode?: string, offset?: number, limit?: number): Promise<IFormsByMarkerDataEntity | IError>;

package/dist/forms-data/formsDataApi.js

@@ -160,6 +160,28 @@ class FormsDataApi extends asyncModules_1.default {
         const validated = await this._validateResponse(result, schema('PostFormResponseSchema'));
         return this._normalizeData(validated);
     }
+    /**
+     * Drops the date bounds the endpoint refuses to parse.
+     *
+     * An empty string means "no filter" on every field of {@link IFormsDataFilter},
+     * and that is still how `entityIdentifier`, `userIdentifier` and an empty
+     * `status` array behave. The date pair is the exception: the endpoint now runs
+     * `dateFrom` / `dateTo` through a date validator before it builds the filter,
+     * so `dateFrom: ''` no longer means "no bound" — it fails the whole request
+     * with `400 dateFrom must be a valid date in format "YYYY-MM-DD"…` and takes
+     * the records down with it. An empty bound is therefore removed from the body
+     * rather than sent, which the API reads as "no bound", the documented meaning.
+     * @param {IFormsDataFilter} body - Filter body as passed by the caller.
+     * @returns {IFormsDataFilter} The same filter without empty date bounds.
+     */
+    _stripEmptyDates(body) {
+        const { dateFrom, dateTo, ...rest } = body;
+        return {
+            ...rest,
+            ...(dateFrom ? { dateFrom } : {}),
+            ...(dateTo ? { dateTo } : {}),
+        };
+    }
     /**
      * Get one object of form data by marker.
      * @handleName getFormsDataByMarker
@@ -179,8 +201,8 @@ class FormsDataApi extends asyncModules_1.default {
      * @param {number} [body.parentId] - Identifier of the parent record, to fetch replies to one submission. Example: 10.
      * @param {string} [body.userIdentifier] - Text identifier of the sender. Example: "admin".
      * @param {FormDataStatus[]} [body.status] - Moderation statuses to keep: "sent", "moderation", "approved", "banned", "deleted". Must be an array; anything outside the set is rejected with `400 each value in status must be a valid enum value`. Example: ["approved"].
-     * @param {string} [body.dateFrom] - Lower bound of the submission date, `YYYY-MM-DD`. An unparsable value fails the request with a `500`. Example: "2025-01-01".
-     * @param {string} [body.dateTo] - Upper bound of the submission date, `YYYY-MM-DD`. Example: "2025-12-31".
+     * @param {string} [body.dateFrom] - Lower bound of the submission date, `YYYY-MM-DD`. An empty string means "no bound" — the SDK removes it from the body, because the endpoint answers `400 dateFrom must be a valid date in format "YYYY-MM-DD"` to one. An unparsable non-empty value still fails the request. Example: "2025-01-01".
+     * @param {string} [body.dateTo] - Upper bound of the submission date, `YYYY-MM-DD`. An empty string means "no bound", handled like `dateFrom`. Example: "2025-12-31".
      * @param {number} [isExtended] - Flag for getting additional fields. Example: 1.
      * @param {string} [langCode] - Language code. Default: "en_US".
      * @param {number} [offset] - Parameter for pagination. Default: 0.
@@ -190,10 +212,12 @@ class FormsDataApi extends asyncModules_1.default {
      * @description Each record's `formData` comes back **already unwrapped from its locale**. The API sends `formData: { "en_US": [ … ] }`; the SDK normalizes the response and hands over the array for `langCode`, so read `record.formData` — `record.formData[langCode]` is `undefined` and yields an empty list with no error. This holds for both values of `isExtended`.
      *
      * The filter body is typed for a reason: the API silently ignores a field it does not know, so a misspelled `statuses` returns every record — unmoderated ones included — and the code looks like it works.
+     *
+     * Empty `dateFrom` / `dateTo` are stripped from the body before it is sent: the endpoint validates the pair as dates and rejects an empty string with a `400`, while every other field still treats "" as "no filter".
      * @see {@link https://js-sdk.oneentry.cloud/docs/forms-data/getFormsDataByMarker getFormsDataByMarker} documentation.
      */
     async getFormsDataByMarker(marker, formModuleConfigId, body = {}, isExtended = 0, langCode = this.state.lang, offset = 0, limit = 30) {
-        const result = await this._fetchPost(`/marker/${marker}?formModuleConfigId=${formModuleConfigId}&isExtended=${isExtended}&langCode=${langCode}&offset=${offset}&limit=${limit}`, body);
+        const result = await this._fetchPost(`/marker/${marker}?formModuleConfigId=${formModuleConfigId}&isExtended=${isExtended}&langCode=${langCode}&offset=${offset}&limit=${limit}`, this._stripEmptyDates(body));
         // Validate response if validation is enabled
         const validated = await this._validateResponse(result, schema('FormsByMarkerDataResponseSchema'));
         return this._normalizeData(validated, langCode);

package/dist/forms-data/formsDataInterfaces.d.ts

@@ -52,7 +52,7 @@ interface IFormsData {
      * @handleName getFormsDataByMarker
      * @param {string} marker - The marker identifying the form data. Example: "contact_form_data".
      * @param {number} formModuleConfigId - The form module configuration ID. Example: 4.
-     * @param {IFormsDataFilter} [body] - Filter for the records to return. Default: {}. Every field is optional; an omitted or empty one is not applied. Valid `status` values: "sent", "moderation", "approved", "banned", "deleted".
+     * @param {IFormsDataFilter} [body] - Filter for the records to return. Default: {}. Every field is optional; an omitted or empty one is not applied — an empty `dateFrom`/`dateTo` is stripped from the body, because the endpoint rejects an empty date with a `400`. Valid `status` values: "sent", "moderation", "approved", "banned", "deleted".
      * @example
         {
           "entityIdentifier": "blog",
@@ -113,8 +113,8 @@ type FormDataStatus = 'sent' | 'moderation' | 'approved' | 'banned' | 'deleted';
  * @property {number} [parentId] - Identifier of the parent record — the way to fetch replies to one comment. Example: 10.
  * @property {string} [userIdentifier] - Text identifier of the sender; an empty string means "no filter". Example: "admin".
  * @property {FormDataStatus[]} [status] - Moderation statuses to keep. Must be an array — a bare string is rejected with `400`. An empty array means "no filter". Example: ["approved"].
- * @property {string} [dateFrom] - Lower bound of the submission date, `YYYY-MM-DD`; an empty string means "no bound". A value the API cannot parse fails the request with a `500`. Example: "2025-01-01".
- * @property {string} [dateTo] - Upper bound of the submission date, `YYYY-MM-DD`; an empty string means "no bound". Example: "2025-12-31".
+ * @property {string} [dateFrom] - Lower bound of the submission date, `YYYY-MM-DD`; an empty string means "no bound" — `getFormsDataByMarker` strips it from the body, since the endpoint rejects an empty date with a `400`. A non-empty value the API cannot parse still fails the request. Example: "2025-01-01".
+ * @property {string} [dateTo] - Upper bound of the submission date, `YYYY-MM-DD`; an empty string means "no bound", handled like `dateFrom`. Example: "2025-12-31".
  * @description Filter for reading form submissions. Every field is optional and an omitted one is simply not applied.
  *
  * Typed rather than left as `object` on purpose: the API **ignores** a field it

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

@@ -77,7 +77,7 @@ interface IListTitleExtended {
  * @type {AttributeType}
  * @description This type defines the possible values for attribute types used in the system.
  */
-type AttributeType = 'string' | 'text' | 'textWithHeader' | 'integer' | 'real' | 'float' | 'dateTime' | 'date' | 'time' | 'file' | 'image' | 'groupOfImages' | 'radioButton' | 'list' | 'button' | 'spam' | 'entity' | 'timeInterval';
+type AttributeType = 'string' | 'text' | 'textWithHeader' | 'integer' | 'real' | 'float' | 'dateTime' | 'date' | 'time' | 'file' | 'image' | 'groupOfImages' | 'radioButton' | 'list' | 'button' | 'spam' | 'entity' | 'timeInterval' | 'json';
 /**
  * Represents an attribute set entity.
  * @interface IAttributesSetsEntity

package/esm/base/attributes.d.ts

@@ -61,7 +61,7 @@ export declare function getAttributeFile(attr: IAttributeValue | undefined): IAt
 /**
  * Narrows an attribute value to a text attribute.
  * @param {IAttributeValue | undefined} attr - The attribute value to test.
- * @returns {boolean} True when the attribute is a `string`, `text` or `textEditor` carrying a string (or nothing).
+ * @returns {boolean} True when the attribute is a `string` or `text` carrying a string (or nothing).
  */
 export declare function isStringAttribute(attr: IAttributeValue | undefined): attr is IStringAttributeValue;
 /**

package/esm/base/attributes.js

@@ -92,13 +92,11 @@ export function getAttributeFile(attr) {
 /**
  * Narrows an attribute value to a text attribute.
  * @param {IAttributeValue | undefined} attr - The attribute value to test.
- * @returns {boolean} True when the attribute is a `string`, `text` or `textEditor` carrying a string (or nothing).
+ * @returns {boolean} True when the attribute is a `string` or `text` carrying a string (or nothing).
  */
 export function isStringAttribute(attr) {
     return (!!attr &&
-        (attr.type === 'string' ||
-            attr.type === 'text' ||
-            attr.type === 'textEditor') &&
+        (attr.type === 'string' || attr.type === 'text') &&
         (attr.value === null || typeof attr.value === 'string'));
 }
 /**

package/esm/base/utils.d.ts

@@ -325,12 +325,12 @@ interface IFileAttributeValue extends IAttributeValue {
 }
 /**
  * @interface IStringAttributeValue
- * @property {'string' | 'text' | 'textEditor'} type - Discriminant identifying the attribute as text-bearing.
+ * @property {'string' | 'text'} type - Discriminant identifying the attribute as text-bearing.
  * @property {string | null} value - The text; `null` when no value is set.
  * @description {@link IAttributeValue} narrowed to text attributes. Narrow to it with `isStringAttribute`.
  */
 interface IStringAttributeValue extends IAttributeValue {
-    type: 'string' | 'text' | 'textEditor';
+    type: 'string' | 'text';
     value: string | null;
 }
 /**

package/esm/forms-data/formsDataApi.d.ts

@@ -60,6 +60,21 @@ export default class FormsDataApi extends AsyncModules implements IFormsData {
      * @see {@link https://js-sdk.oneentry.cloud/docs/forms-data/postFormsData postFormsData} documentation.
      */
     postFormsData(body: IBodyPostFormData, langCode?: string): Promise<IPostFormResponse | IError>;
+    /**
+     * Drops the date bounds the endpoint refuses to parse.
+     *
+     * An empty string means "no filter" on every field of {@link IFormsDataFilter},
+     * and that is still how `entityIdentifier`, `userIdentifier` and an empty
+     * `status` array behave. The date pair is the exception: the endpoint now runs
+     * `dateFrom` / `dateTo` through a date validator before it builds the filter,
+     * so `dateFrom: ''` no longer means "no bound" — it fails the whole request
+     * with `400 dateFrom must be a valid date in format "YYYY-MM-DD"…` and takes
+     * the records down with it. An empty bound is therefore removed from the body
+     * rather than sent, which the API reads as "no bound", the documented meaning.
+     * @param {IFormsDataFilter} body - Filter body as passed by the caller.
+     * @returns {IFormsDataFilter} The same filter without empty date bounds.
+     */
+    private _stripEmptyDates;
     /**
      * Get one object of form data by marker.
      * @handleName getFormsDataByMarker
@@ -79,8 +94,8 @@ export default class FormsDataApi extends AsyncModules implements IFormsData {
      * @param {number} [body.parentId] - Identifier of the parent record, to fetch replies to one submission. Example: 10.
      * @param {string} [body.userIdentifier] - Text identifier of the sender. Example: "admin".
      * @param {FormDataStatus[]} [body.status] - Moderation statuses to keep: "sent", "moderation", "approved", "banned", "deleted". Must be an array; anything outside the set is rejected with `400 each value in status must be a valid enum value`. Example: ["approved"].
-     * @param {string} [body.dateFrom] - Lower bound of the submission date, `YYYY-MM-DD`. An unparsable value fails the request with a `500`. Example: "2025-01-01".
-     * @param {string} [body.dateTo] - Upper bound of the submission date, `YYYY-MM-DD`. Example: "2025-12-31".
+     * @param {string} [body.dateFrom] - Lower bound of the submission date, `YYYY-MM-DD`. An empty string means "no bound" — the SDK removes it from the body, because the endpoint answers `400 dateFrom must be a valid date in format "YYYY-MM-DD"` to one. An unparsable non-empty value still fails the request. Example: "2025-01-01".
+     * @param {string} [body.dateTo] - Upper bound of the submission date, `YYYY-MM-DD`. An empty string means "no bound", handled like `dateFrom`. Example: "2025-12-31".
      * @param {number} [isExtended] - Flag for getting additional fields. Example: 1.
      * @param {string} [langCode] - Language code. Default: "en_US".
      * @param {number} [offset] - Parameter for pagination. Default: 0.
@@ -90,6 +105,8 @@ export default class FormsDataApi extends AsyncModules implements IFormsData {
      * @description Each record's `formData` comes back **already unwrapped from its locale**. The API sends `formData: { "en_US": [ … ] }`; the SDK normalizes the response and hands over the array for `langCode`, so read `record.formData` — `record.formData[langCode]` is `undefined` and yields an empty list with no error. This holds for both values of `isExtended`.
      *
      * The filter body is typed for a reason: the API silently ignores a field it does not know, so a misspelled `statuses` returns every record — unmoderated ones included — and the code looks like it works.
+     *
+     * Empty `dateFrom` / `dateTo` are stripped from the body before it is sent: the endpoint validates the pair as dates and rejects an empty string with a `400`, while every other field still treats "" as "no filter".
      * @see {@link https://js-sdk.oneentry.cloud/docs/forms-data/getFormsDataByMarker getFormsDataByMarker} documentation.
      */
     getFormsDataByMarker(marker: string, formModuleConfigId: number, body?: IFormsDataFilter, isExtended?: number, langCode?: string, offset?: number, limit?: number): Promise<IFormsByMarkerDataEntity | IError>;

package/esm/forms-data/formsDataApi.js

@@ -122,6 +122,28 @@ export default class FormsDataApi extends AsyncModules {
         const validated = await this._validateResponse(result, schema('PostFormResponseSchema'));
         return this._normalizeData(validated);
     }
+    /**
+     * Drops the date bounds the endpoint refuses to parse.
+     *
+     * An empty string means "no filter" on every field of {@link IFormsDataFilter},
+     * and that is still how `entityIdentifier`, `userIdentifier` and an empty
+     * `status` array behave. The date pair is the exception: the endpoint now runs
+     * `dateFrom` / `dateTo` through a date validator before it builds the filter,
+     * so `dateFrom: ''` no longer means "no bound" — it fails the whole request
+     * with `400 dateFrom must be a valid date in format "YYYY-MM-DD"…` and takes
+     * the records down with it. An empty bound is therefore removed from the body
+     * rather than sent, which the API reads as "no bound", the documented meaning.
+     * @param {IFormsDataFilter} body - Filter body as passed by the caller.
+     * @returns {IFormsDataFilter} The same filter without empty date bounds.
+     */
+    _stripEmptyDates(body) {
+        const { dateFrom, dateTo, ...rest } = body;
+        return {
+            ...rest,
+            ...(dateFrom ? { dateFrom } : {}),
+            ...(dateTo ? { dateTo } : {}),
+        };
+    }
     /**
      * Get one object of form data by marker.
      * @handleName getFormsDataByMarker
@@ -141,8 +163,8 @@ export default class FormsDataApi extends AsyncModules {
      * @param {number} [body.parentId] - Identifier of the parent record, to fetch replies to one submission. Example: 10.
      * @param {string} [body.userIdentifier] - Text identifier of the sender. Example: "admin".
      * @param {FormDataStatus[]} [body.status] - Moderation statuses to keep: "sent", "moderation", "approved", "banned", "deleted". Must be an array; anything outside the set is rejected with `400 each value in status must be a valid enum value`. Example: ["approved"].
-     * @param {string} [body.dateFrom] - Lower bound of the submission date, `YYYY-MM-DD`. An unparsable value fails the request with a `500`. Example: "2025-01-01".
-     * @param {string} [body.dateTo] - Upper bound of the submission date, `YYYY-MM-DD`. Example: "2025-12-31".
+     * @param {string} [body.dateFrom] - Lower bound of the submission date, `YYYY-MM-DD`. An empty string means "no bound" — the SDK removes it from the body, because the endpoint answers `400 dateFrom must be a valid date in format "YYYY-MM-DD"` to one. An unparsable non-empty value still fails the request. Example: "2025-01-01".
+     * @param {string} [body.dateTo] - Upper bound of the submission date, `YYYY-MM-DD`. An empty string means "no bound", handled like `dateFrom`. Example: "2025-12-31".
      * @param {number} [isExtended] - Flag for getting additional fields. Example: 1.
      * @param {string} [langCode] - Language code. Default: "en_US".
      * @param {number} [offset] - Parameter for pagination. Default: 0.
@@ -152,10 +174,12 @@ export default class FormsDataApi extends AsyncModules {
      * @description Each record's `formData` comes back **already unwrapped from its locale**. The API sends `formData: { "en_US": [ … ] }`; the SDK normalizes the response and hands over the array for `langCode`, so read `record.formData` — `record.formData[langCode]` is `undefined` and yields an empty list with no error. This holds for both values of `isExtended`.
      *
      * The filter body is typed for a reason: the API silently ignores a field it does not know, so a misspelled `statuses` returns every record — unmoderated ones included — and the code looks like it works.
+     *
+     * Empty `dateFrom` / `dateTo` are stripped from the body before it is sent: the endpoint validates the pair as dates and rejects an empty string with a `400`, while every other field still treats "" as "no filter".
      * @see {@link https://js-sdk.oneentry.cloud/docs/forms-data/getFormsDataByMarker getFormsDataByMarker} documentation.
      */
     async getFormsDataByMarker(marker, formModuleConfigId, body = {}, isExtended = 0, langCode = this.state.lang, offset = 0, limit = 30) {
-        const result = await this._fetchPost(`/marker/${marker}?formModuleConfigId=${formModuleConfigId}&isExtended=${isExtended}&langCode=${langCode}&offset=${offset}&limit=${limit}`, body);
+        const result = await this._fetchPost(`/marker/${marker}?formModuleConfigId=${formModuleConfigId}&isExtended=${isExtended}&langCode=${langCode}&offset=${offset}&limit=${limit}`, this._stripEmptyDates(body));
         // Validate response if validation is enabled
         const validated = await this._validateResponse(result, schema('FormsByMarkerDataResponseSchema'));
         return this._normalizeData(validated, langCode);

package/esm/forms-data/formsDataInterfaces.d.ts

@@ -52,7 +52,7 @@ interface IFormsData {
      * @handleName getFormsDataByMarker
      * @param {string} marker - The marker identifying the form data. Example: "contact_form_data".
      * @param {number} formModuleConfigId - The form module configuration ID. Example: 4.
-     * @param {IFormsDataFilter} [body] - Filter for the records to return. Default: {}. Every field is optional; an omitted or empty one is not applied. Valid `status` values: "sent", "moderation", "approved", "banned", "deleted".
+     * @param {IFormsDataFilter} [body] - Filter for the records to return. Default: {}. Every field is optional; an omitted or empty one is not applied — an empty `dateFrom`/`dateTo` is stripped from the body, because the endpoint rejects an empty date with a `400`. Valid `status` values: "sent", "moderation", "approved", "banned", "deleted".
      * @example
         {
           "entityIdentifier": "blog",
@@ -113,8 +113,8 @@ type FormDataStatus = 'sent' | 'moderation' | 'approved' | 'banned' | 'deleted';
  * @property {number} [parentId] - Identifier of the parent record — the way to fetch replies to one comment. Example: 10.
  * @property {string} [userIdentifier] - Text identifier of the sender; an empty string means "no filter". Example: "admin".
  * @property {FormDataStatus[]} [status] - Moderation statuses to keep. Must be an array — a bare string is rejected with `400`. An empty array means "no filter". Example: ["approved"].
- * @property {string} [dateFrom] - Lower bound of the submission date, `YYYY-MM-DD`; an empty string means "no bound". A value the API cannot parse fails the request with a `500`. Example: "2025-01-01".
- * @property {string} [dateTo] - Upper bound of the submission date, `YYYY-MM-DD`; an empty string means "no bound". Example: "2025-12-31".
+ * @property {string} [dateFrom] - Lower bound of the submission date, `YYYY-MM-DD`; an empty string means "no bound" — `getFormsDataByMarker` strips it from the body, since the endpoint rejects an empty date with a `400`. A non-empty value the API cannot parse still fails the request. Example: "2025-01-01".
+ * @property {string} [dateTo] - Upper bound of the submission date, `YYYY-MM-DD`; an empty string means "no bound", handled like `dateFrom`. Example: "2025-12-31".
  * @description Filter for reading form submissions. Every field is optional and an omitted one is simply not applied.
  *
  * Typed rather than left as `object` on purpose: the API **ignores** a field it

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "oneentry",
-  "version": "1.0.164",
+  "version": "1.0.165",
   "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.164"
+    "postpublish": "node ../scripts/verify-published.js --named defineOneEntry --expect 1.0.165"
   },
   "sideEffects": false,
   "files": [