🎨 Palette: Add progress indicator and icon to call chain UX

[AhmmedSamier]

💡 What: Added a vscode.window.withProgress indicator around the asynchronous call chain building process, and added the standard $(call-incoming) Codicon to the "visualize call chain" CodeLens title.

🎯 Why: The call chain builder performs deep symbol and reference resolution which can be slow on large codebases. The lack of a loading indicator left the user wondering if the click registered. Adding an icon improves feature discoverability and aligns with standard VS Code visual patterns.

📸 Before/After: Before, clicking "visualize call chain" had no immediate feedback, and the CodeLens was plain text. After, clicking shows a VS Code progress notification, and the CodeLens includes a relevant icon.

♿ Accessibility: The loading state improves overall UX clarity by preventing users from repeatedly clicking the action or thinking the UI has frozen.

---

PR created automatically by Jules for task 14334957871898965257 started by @AhmmedSamier

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[coderabbitai]

Warning

Rate limit exceeded

@AhmmedSamier has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 9 minutes and 49 seconds before requesting another review.

To continue reviewing without waiting, purchase usage credits in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 4d3b9cd5-2873-431a-8c32-5665019f4589

📥 Commits

Reviewing files that changed from the base of the PR and between b237974 and ee457c4.

📒 Files selected for processing (2)

• vscode-extension/src/extension.ts
• vscode-extension/src/reference-code-lens.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch palette-call-chain-ux-14334957871898965257

---

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

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