Provide custom comparer support for in-memory QuickGrid sorting

[VigneshwaranGovindharajan]

Provide custom comparer support for in-memory QuickGrid sorting

Description

Adds support for custom comparisons in QuickGrid sorting by accepting an IComparer on GridSort and exposing comparer usage on PropertyColumn. This enables consumers to supply custom ordering (for example, sort strings by length, by vowel count, or integers by absolute value) when the data is materialized in memory.

Important: custom comparers are supported only when sorting is performed in-memory (LINQ-to-Objects). They cannot be translated to SQL/EF Core; trying to use comparers with remote IQueryable providers will not work and may cause runtime translation failures. Documentation and XML remarks call this out.

Changes:

• Added comparer overloads on GridSort:

• ByAscending(Expression<Func<T, U>> keySelector, IComparer comparer)

• ByDescending(Expression<Func<T, U>> keySelector, IComparer comparer)

• ThenAscending(Expression<Func<T, U>> keySelector, IComparer comparer)

• ThenDescending(Expression<Func<T, U>> keySelector, IComparer comparer)

• Each overload includes XML docs noting the in-memory-only restriction.

• PropertyColumn<T, TProp>:

• New [Parameter] public IComparer? Comparer { get; set; }

• Column builds the column's sort specification using the comparer when provided.

• Tracks comparer changes so the column updates SortBy when the comparer parameter changes.

• Wiring:

• GridItemsProviderRequest.ApplySorting(IQueryable) already calls SortByColumn?.SortBy?.Apply(...). The GridSort comparer overloads pass the comparer through to LINQ OrderBy/ThenBy overloads when the source is in-memory.

Fixes #45478

[dotnet-policy-service]

Thanks for your PR, @VigneshwaranGovindharajan. Someone from the team will get assigned to your PR shortly and we'll get it reviewed.

[VigneshwaranGovindharajan]

#67035

[VigneshwaranGovindharajan]

@dotnet-policy-service agree company="Syncfusion, Inc."