Skip to content
This repository was archived by the owner on Jan 23, 2026. It is now read-only.

DevMode: remove mouse tracking as it caused the inability to copy/paste in the terminal#316

Merged
jhaynie merged 2 commits intomainfrom
tui-improvements
May 20, 2025
Merged

DevMode: remove mouse tracking as it caused the inability to copy/paste in the terminal#316
jhaynie merged 2 commits intomainfrom
tui-improvements

Conversation

@jhaynie
Copy link
Copy Markdown
Member

@jhaynie jhaynie commented May 20, 2025

Summary by CodeRabbit

  • Refactor
    • Removed mouse interaction support from the developer UI, simplifying log display to keyboard-only navigation.
    • Log entries no longer have unique IDs, resulting in a cleaner and more streamlined interface.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 20, 2025

Walkthrough

The changes remove all dependencies and code related to mouse interaction and the bubblezone package from the TUI component. The log item structure is simplified by eliminating unique IDs and zone marking. The go.mod file is updated to remove the bubblezone dependency, and mouse event handling logic is deleted from the UI.

Changes

File(s) Change Summary
go.mod Removed github.com/lrstanley/bubblezone dependency from the require section.
internal/dev/tui.go Removed all bubblezone and uuid references, deleted mouse interaction logic, simplified log item struct and methods, and removed mouse event handling from the UI.

Poem

In the garden of code, a mouse once did roam,
But now the logs stand quietly alone.
No zones, no clicks, just messages clear—
The TUI’s simpler, with nothing to fear.
🐇 With dependencies trimmed and clutter all gone,
The rabbit hops forward, the journey goes on!

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.


Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between c718196 and 8a5e59d.

📒 Files selected for processing (1)
  • internal/dev/tui.go (3 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • internal/dev/tui.go
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Build and Test (windows-latest)
  • GitHub Check: Test CLI Upgrade Path (windows-latest)
  • GitHub Check: Analyze (go)
✨ Finishing Touches
  • 📝 Generate Docstrings

🪧 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.
    • Explain this complex logic.
    • 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. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • 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 src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

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

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

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

Documentation and Community

  • 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.

@jhaynie jhaynie requested a review from pec1985 May 20, 2025 16:31
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🔭 Outside diff range comments (1)
internal/dev/tui.go (1)

550-575: ⚠️ Potential issue

Potential nil-pointer panic when stopping the spinner

SetSpinner(false) unconditionally calls d.spinnerCancel().
If the caller invokes SetSpinner(false) before any preceding SetSpinner(true) (or twice in a row), spinnerCancel is still nil and the program will panic.

Proposed safeguard:

-} else {
-    d.spinnerCancel()
-    d.spinnerCtx = nil
-    d.program.Send(spinnerStopMsg{})
+} else if d.spinnerCancel != nil {
+    d.spinnerCancel()
+    d.spinnerCtx = nil
+    d.program.Send(spinnerStopMsg{})
 }

This keeps existing behaviour while eliminating the panic path.

🧹 Nitpick comments (1)
internal/dev/tui.go (1)

62-70: Title and FilterValue now return identical strings – reconsider uniqueness guarantees

After removing the id/zone logic both methods just echo message.
list.Model uses FilterValue when searching; duplicate messages will all match, which is fine.
• However Title is what’s rendered; if several log lines share the same text they will be visually indistinguishable and impossible to select unambiguously once the mouse-zone IDs are gone.

If you expect duplicate messages, consider prefixing with the timestamp (or its short form) to keep each row unique and still human-readable.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 0054782 and c718196.

⛔ Files ignored due to path filters (1)
  • go.sum is excluded by !**/*.sum
📒 Files selected for processing (2)
  • go.mod (0 hunks)
  • internal/dev/tui.go (2 hunks)
💤 Files with no reviewable changes (1)
  • go.mod
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Test CLI Upgrade Path (windows-latest)
  • GitHub Check: Build and Test (windows-latest)
  • GitHub Check: Analyze (go)
🔇 Additional comments (1)
internal/dev/tui.go (1)

384-384: LGTM – view rendering works without zone.Scan

The new fmt.Sprintf("%s\n%s\n%s", …) is a clean replacement now that zones are gone.
No functional issues spotted.

Copy link
Copy Markdown
Contributor

@pec1985 pec1985 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

MERGE IT

@jhaynie jhaynie merged commit 3d85663 into main May 20, 2025
15 checks passed
@jhaynie jhaynie deleted the tui-improvements branch May 20, 2025 16:51
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants