Feature/query store grid - Bar chart and descending first sort

[rferraton]

What does this PR do?

Changes on the query store grid :

• add bar charts into the grid with theme config possible in the BarChartConfig.axml for bar colors of selected column used for sorting and the others or even the possibility to custom colors for all columns independently
• Descending sort first when clicking on column header in the QS grid

Which component(s) does this affect?

• Desktop App (PlanViewer.App)
• Core Library (PlanViewer.Core)
• CLI Tool (PlanViewer.Cli)
• SSMS Extension (PlanViewer.Ssms)
• Tests
• Documentation

How was this tested?

Describe the testing you've done. Include:

• Plan files tested : none only grid impact
• Platforms tested : Windows

Checklist

• I have read the contributing guide
• My code builds with zero warnings (dotnet build -c Debug)
• All tests pass (dotnet test)
• I have not introduced any hardcoded credentials or server names

Summary by CodeRabbit

• New Features
  • Added visual bar charts to the query metrics display, showing relative values for executions, CPU usage, duration, reads, writes, and memory.
  • Implemented custom sorting with visual indicators to highlight the currently sorted column.
  • Added configurable color scheme for bar chart visualization to support custom theming.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: f64ae344-45e9-4205-b072-ff8f0c9247f5

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

📝 Coding Plan

• Generate coding plan for human review comments

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Tip

CodeRabbit can approve the review once all CodeRabbit's comments are resolved.

Enable the reviews.request_changes_workflow setting to automatically approve the review once all CodeRabbit's comments are resolved.

[erikdarlingdata]

Thanks for the contribution! The bar charts and descending-first sort are both great UX additions for performance data. A few things to address before merge:

Must fix

1. Rebase on current dev — This PR is based on code before several recent changes. Current dev has:

   • 3 new columns between PlanId and Last Executed: Query Hash, Plan Hash, Module (PR #93)
   • "View History" context menu item (PR #98)
   • Code review fixes including dead code removal and CTS disposal (PR #97)

   You'll need to rebase on current dev and resolve conflicts. The new columns should be preserved (as plain text columns — they're identifiers, not metrics, so bar charts don't apply to them).

2. Missing sort keys — GetSortKey switch doesn't handle QueryHash, QueryPlanHash, or ModuleName columns (added in #93). Sorting on those columns would fall through to the LastExecutedLocal default. Add cases for them.

Suggestions (non-blocking)

3. Property boilerplate — The 13 ratio properties + 13 isSorted properties + SetBar switch adds ~130 lines of repetitive code to QueryStoreRow. A dictionary-based approach (e.g., Dictionary<string, (double Ratio, bool IsSorted)> with a single indexer or GetRatio(columnId) method) would be significantly leaner. Not a blocker since the current approach works correctly.

4. UpdateBarRatios efficiency — Currently calls .Max() 13 times across all filtered rows. Could be computed in a single pass over the rows, accumulating max values for all columns simultaneously. Again, not a blocker for typical grid sizes (25-100 rows).

The feature itself looks solid — clean BarChartCell control, good theme configurability, and the sort cycle (desc → asc → clear) makes sense for this context. Just needs the rebase to integrate with recent changes.

[rferraton]

go to fix a rebase from dev ...