Fixed: error setting default sort for non-string properties #754
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@fdlane does this solve your issue? |
|
@bart-degreed the non-string properties now sort with correctly. Thank you! public override PropertySortOrder GetDefaultSortOrder() => new PropertySortOrder
{
(t => t.InvoiceDate, SortDirection.Descending)
}; |
38 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes the problem described at #741 (comment).
The issue is that the specified expression gets wrapped in a type conversion expression on non-string properties, making the code unable to 'see' through the single field.
Unfortunately this code is shared between GetDefaultSortOrder and HideFields, making it possible to specify multiple fields in a single ordering (which makes no sense at all).