Lite - fixed sort on columns that are formatted for seconds or milliseconds - branch fixed#452
Merged
erikdarlingdata merged 2 commits intoerikdarlingdata:devfrom Mar 6, 2026
Conversation
Release v2.1.0
…, miliseconds or both to order correctly. - Used the SortMemberPath property to point to the numeric value. - Increased some widths of columns to ensure complete header is shown.
erikdarlingdata
approved these changes
Mar 6, 2026
Owner
erikdarlingdata
left a comment
There was a problem hiding this comment.
Looks good — clean, minimal fix. All 7 SortMemberPath additions point to real numeric properties on the backing model classes (DurationMs, SqlDurationMs, DuckDbDurationMs, AvgDurationMs). Column width bumps are reasonable.
Approved and merging. I'll open a follow-up issue for other formatted duration columns elsewhere in the app that have the same mixed-unit sorting problem.
This was referenced Mar 6, 2026
This file contains hidden or 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
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.
What does this PR do?
This PR fixes bug/issue #450.
Which component(s) does this affect?
How was this tested?
Describe the testing you've done. Include:
Checklist
dotnet build -c Debug)