IgxGrid: Multi-column sorting does not work if custom sortStrategy is used

[mkamiishi]

Description

In this sample(https://stackblitz.com/edit/angular-pjwndf-qa8ref?file=src/app/grid/grid-sorting-sample/grid-sorting-sample.component.html) ‘Fruit’ and ‘Company Name’ columns use a custom sortStrategy so that ‘Fruit’ column uses ‘fruitIndex’ column data and ‘Company Name’ column uses ‘companyIndex’ column data respectively when they are sorted.
Now when multi-column sorting is applied, for example, 1st sort by ‘Group’ column, 2nd sort by ‘Fruit’ column, and 3rd sort by ‘Company Name’ column, the 2nd sort does not work as expected.

• igniteui-angular version: 15.1.1
• browser: Chrome

Steps to reproduce

Run the sample:https://stackblitz.com/edit/angular-pjwndf-qa8ref?file=src/app/grid/grid-sorting-sample/grid-sorting-sample.component.html

Result

Multi-column sorting does not work as expected.

Expected result

Multi-column sorting works with a custom sortStrategy.

[mkamiishi]

Issue#12611(#12611) was not fixed properly.

[viktorkombov]

@mkamiishi, I noticed that in the provided sample you are trying to sort the records using the first two arguments of the custom groupingComparer function. Keep in mind that the first two arguments are only the values of the column that is sorted. If you would like to compare the records by their other properties you should use the third and the forth arguments of the groupingComparer function:

igniteui-angular/projects/igniteui-angular/src/lib/data-operations/grouping-expression.interface.ts

Lines 3 to 5 in 4f3aba8

	export interface IGroupingExpression extends ISortingExpression {
	groupingComparer?: (a: any, b: any, currRec?: any, groupRec?: any) => number;
	}

I have modified the sample in order to sort by the other properties of the records:

customGroupingComparer = (a: any, b: any, currRec: any, groupRec: any) => {
           return currRec.fruitIndex === groupRec.fruitIndex ? 0 : -1;
};

Could you please test the sample on your side and let me know whether the issue is still reproducible?

[mkamiishi]

@viktorkombov
It works as expected with the suggested code.
Thank you!