UN-2742 [FIX] Show profile name instead of LLM name in Output Analyzer tabs#2030
UN-2742 [FIX] Show profile name instead of LLM name in Output Analyzer tabs#2030athul-rs wants to merge 1 commit into
Conversation
Profiles encode user intent (same model can differ by LLMWhisperer mode, chunking, etc.), so the profile name is the meaningful label when comparing outputs. The LLM model name stays available as a tooltip on each tab. Applies to the shared tab strip used by the Output Analyzer and the main combined-output view (JsonView), and the same pattern in OutputForDocModal. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Frontend Lint Report (Biome)✅ All checks passed! No linting or formatting issues found. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
Summary by CodeRabbit
WalkthroughTwo output components add Ant Design ChangesAdapter Model Tooltips
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
|
|
| Filename | Overview |
|---|---|
| frontend/src/components/custom-tools/combined-output/JsonView.jsx | Added Tooltip import; tab label priority flipped from llm_model |
| frontend/src/components/custom-tools/output-for-doc-modal/OutputForDocModal.jsx | Same Tooltip-wrapping pattern applied consistently; tab selection (handleTabChange) is keyed on index, unchanged by the label swap |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[adapterData array] --> B{profile_name truthy?}
B -- Yes --> C[Tab label = profile_name]
B -- No --> D[Tab label = llm_model]
C --> E{llm_model defined?}
D --> E
E -- Yes --> F[Tooltip shows llm_model on hover]
E -- No --> G[No tooltip rendered]
F --> H[Tab rendered in strip]
G --> H
Reviews (1): Last reviewed commit: "UN-2742 Show profile name instead of LLM..." | Re-trigger Greptile



What
Why
UN-2742 — users create profiles with specific intent (the same model can be used with different LLMWhisperer modes, chunking, retrieval settings). When comparing outputs across profiles, the model name is ambiguous — two tabs can read identically while being different profiles. The profile name is the meaningful identity; the model is secondary context, now preserved in a tooltip.
How
combined-output/JsonView.jsx— flipped label preference toprofile_name || llm_model, wrapped in<Tooltip title={llm_model}>. This is the shared tab strip used by both the Output Analyzer and the main combined-output view, so both stay consistent.output-for-doc-modal/OutputForDocModal.jsx— same pattern applied to the identical tab strip there.Can this PR break any existing features. If yes, please list possible items. If no, please explain why. (PS: Admins do not merge the PR without this section filled)
profile_id(JsonView) / index (OutputForDocModal), never on the label text, so behavior is unchanged — only the visible label flips. No tests, e2e selectors, or CSS reference the label text.profile_nameis a required, whitespace-validated field at profile creation, so labels can't be blank. If a profile's adapter was deleted (no resolvable model), the tooltip simply doesn't render (antd disables tooltips with undefined title) — previously that case showed the profile name with no tooltip, so nothing is lost.Database Migrations
Env Config
Relevant Docs
Related Issues or PRs
Dependent Features
Notes on Testing
vite buildsucceeds.Screenshots
N/A
Checklist
I have read and understood the Contribution Guidelines.
🤖 Generated with Claude Code