FilterBuilder: fix invalid date formatting (T1319193, T1311486)

[anna-shakhova]

No description provided.

[Copilot]

Pull request overview

Fixes FilterBuilder’s handling of invalid date values by preventing attempts to format invalid Date instances and expanding/relocating related test coverage.

Changes:

• Treat invalid Date objects as invalid input in formatHelper.format() (returning value.toString() instead of passing them to date localization formatting).
• Adjust FilterBuilder value formatting to avoid coercing non-string/non-numeric values into Date objects.
• Update/add tests: expand formatHelper.format() coverage and move FilterBuilder formatting tests from QUnit to Jest (plus add a regression case).

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
packages/devextreme/testing/tests/DevExpress.utils/utils.formatHelper.tests.js	Switches to ESM import and adds QUnit coverage for formatHelper.format() edge cases (including invalid dates).
packages/devextreme/testing/tests/DevExpress.ui.widgets/filterBuilderParts/utilsTests.js	Removes the old QUnit “Formatting” module tests (migrated to Jest).
packages/devextreme/js/format_helper.js	Prevents formatting invalid Date values by validating getTime() before delegating to date localization.
packages/devextreme/js/__internal/filter_builder/m_utils.ts	Updates FilterBuilder value-to-text formatting (incl. typed refactor) to avoid unintended Date coercions.
packages/devextreme/js/__internal/filter_builder/tests/utils.test.ts	Adds Jest coverage for FilterBuilder value formatting, including an invalid date string regression.

[Copilot]

Pull request overview

Copilot reviewed 9 out of 12 changed files in this pull request and generated 4 comments.

[Copilot]

Pull request overview

Copilot reviewed 9 out of 12 changed files in this pull request and generated 2 comments.

Comments suppressed due to low confidence (1)

packages/devextreme/js/__internal/filter_builder/m_utils.ts:604

• New // @ts-expect-error suppressions were added for the customizeText payload. Rather than relying on suppression comments, it would be more robust to define an explicit internal payload type (or cast the payload to any in one place) so the expected shape is clear and future type changes don't get silently masked.

    valueText = field.customizeText.call(field, {
      // @ts-expect-error
      value,
      valueText,
      target,
    });

[Copilot]

Test name grammar: "Proper handle ..." → "Properly handle ...".

Suggested change

	test('Proper handle custom filter operations for dates with non-date values', async (t) => {
	test('Properly handle custom filter operations for dates with non-date values', async (t) => {

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[Alyar666]

The filter range start/end editor can also be NumberBox