Fixed #14432

[fabiolucenaribas]

Performing the fix for the filters and maintaining the global filtering behavior

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
primeng	⬜️ Ignored (Inspect)	Visit Preview		Dec 26, 2023 8:53pm

[cetincakiroglu]

Hi,

You should use filterGlobal method instead of modifying filter method, it's not for global filtering. Please see the example: https://stackblitz.com/edit/github-8nu6jf?file=src%2Fapp%2Fapp.component.ts

I've reverted this PR in #15053 because it introduced new breaking changes in #14588 and #14903

[fabiolucenaribas]

@cetincakiroglu

This is a filter-specific correction, solving the problem when there are multiple filters for the same field (complex), however I understand that it has generated an unintended impact on simple filters

this.filters[field] = field == 'global'? { value: value, matchMode: matchMode } : [{ value: value, matchMode: matchMode }];

    filter(value: any, field: string, matchMode: string) {
        if (this.filterTimeout) {
            clearTimeout(this.filterTimeout);
        }
        if (!this.isFilterBlank(value)) {
            this.filters[field] = { value: value, matchMode: matchMode };
            this.filters[field] = field == 'global'? { value: value, matchMode: matchMode } : [{ value: value, matchMode: matchMode }];
        } else if (this.filters[field]) {
            delete this.filters[field];
        }
        this.filterTimeout = setTimeout(() => {
            this._filter();
            this.filterTimeout = null;
        }, this.filterDelay);
        this.anchorRowIndex = null;
    }
    filterGlobal(value: any, matchMode: string) {
        this.filter(value, 'global', matchMode);
    }

The mention of the 'global' type within the filter function is to maintain the existing behavior given that the 'filterGlobal' function calls the 'filter'

    filterGlobal(value: any, matchMode: string) {
        this.filter(value, 'global', matchMode);
    }

It is necessary to look for a solution that meets both scenarios of #14433 and #14903,
#14433 In the example mentioned, the error occurred when the field in the interface has more than one filter

Expected outcome:

*I'm using the English translator, sorry if I don't express myself well