fix: control panel selection

[coodos]

Description of change

Issue Number

Type of change

• Breaking (any change that would cause existing functionality to not work as expected)
• New (a change which implements a new feature)
• Update (a change which updates existing functionality)
• Fix (a change which fixes an issue)
• Docs (changes to the documentation)
• Chore (refactoring, build scripts or anything else that isn't user-facing)

How the change has been tested

Change checklist

• I have ensured that the CI Checks pass locally
• I have removed any unnecessary logic
• My code is well documented
• I have signed my commits
• My code follows the pattern of the application
• I have self reviewed my code

Summary by CodeRabbit

• Bug Fixes

  • Improved reliability of table selection checkboxes: item checkboxes now stay in sync with selected items, the “Select All” header accurately reflects current selections, and selection states reset appropriately when table data changes.

• Chores

  • Added diagnostic logging around selection and “Select All” actions to support troubleshooting without changing user-facing behavior.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Introduces state-based checkbox management in Table.svelte with effects to reset and sync check states to tableData and selectedIndices, plus detailed debug logging. Adds debug logs to “select all” handlers in +page.svelte. No public API changes.

Changes

Cohort / File(s)	Summary
Table checkbox state sync infrastructure/control-panel/src/lib/ui/Table/Table.svelte	Converted reactive array to state array for checkItems. Added effect to reset checkItems on tableData change. Expanded sync effect to compute per-index shouldBeChecked, update checkAll, and add detailed logs. Core toggle handlers unchanged aside from new state shape.
Page-level select-all logging infrastructure/control-panel/src/routes/+page.svelte	Added debug logs to handleSelectAllEVaults and handleSelectAllPlatforms, including invocation details, item counts, resulting selected indices, and persisted sessionStorage values. No logic or API changes.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  actor User
  participant Data as tableData
  participant Table as Table.svelte
  participant Reset as Effect: Reset on tableData
  participant Sync as Effect: Sync on selectedIndices
  participant Header as checkAll

  Note over Table: Initialize state: checkItems = []<br/>selectedIndices provided externally

  User->>Data: Change tableData
  Data->>Reset: Trigger
  Reset->>Table: Set checkItems = [false...]
  Reset-->>Header: Set checkAll = false

  User->>Table: Update selections (selectedIndices)
  Table->>Sync: Trigger
  Sync->>Table: For each index: checkItems[i] = selectedIndices.includes(i)
  Sync-->>Header: Update checkAll based on all-checked
  Note right of Sync: Logs per-checkbox and final states

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I tick and I tock with a checkbox cheer,
Logs like carrots, crunchy and clear.
Reset the rows, align each ear—
Select them all? The path is near.
Hop, sync, hop—no fear, no fall,
A tidy warren for “check all.” 🥕

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 2cb9322 and ab02690.

📒 Files selected for processing (2)

• infrastructure/control-panel/src/lib/ui/Table/Table.svelte (1 hunks)
• infrastructure/control-panel/src/routes/+page.svelte (1 hunks)

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/control-panel-selection

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.