fix(web): studio grid and research search polish#377
Conversation
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the 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 configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
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 |
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request focuses on polishing the user interface for the research search box and the studio paper gallery. The changes address visual inconsistencies, specifically an overlapping rounded-corner effect in the search box and a desire to switch to a more refined per-card border display in the paper grid. This PR also serves as a rebuild of previous UI changes on top of the current main branch to resolve code-scanning rule blocks from historical commits, ensuring fresh CodeQL and CI results. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Pull request overview
Rebuilds UI polish changes from blocked PR #374: fixes overlapping rounded corners in the research search box and switches the studio paper grid from a framed gap-based layout to per-card single-line borders.
Changes:
- Studio
PaperGallerygrid switched fromgap-pxwith colored background togap-0with conditional per-card borders for clean single-width separators - Research
SearchBoxtextarea getsoverflow-hiddenon container and!importantstyle resets to prevent double rounded-corner artifacts
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
web/src/components/studio/PaperGallery.tsx |
Replace gap-based grid border trick with per-card conditional border classes |
web/src/components/research/SearchBox.tsx |
Add overflow-hidden and force-reset textarea border/radius/shadow |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces several UI polishing changes. In the research search box, it fixes an overlapping rounded-corner issue by using overflow-hidden and resetting the inner Textarea styles. For the studio paper gallery, it refactors the grid from a gap-based border simulation to explicit borders on each card, which improves clarity. The changes are well-implemented and achieve the desired visual results. I've left one comment regarding a minor code cleanup for better maintainability.
| disabled={disabled || isSearching} | ||
| className={cn( | ||
| "min-h-[56px] max-h-[200px] resize-none border-0 bg-transparent", | ||
| "min-h-[56px] max-h-[200px] resize-none border-0 bg-transparent !rounded-none !border-0 !shadow-none", |
There was a problem hiding this comment.
This line includes both border-0 and !border-0. While tailwind-merge correctly resolves this by prioritizing the !border-0 class (due to the !important flag), including the redundant border-0 class can be confusing for future maintenance. It's best to remove the redundant class for improved code clarity.
| "min-h-[56px] max-h-[200px] resize-none border-0 bg-transparent !rounded-none !border-0 !shadow-none", | |
| "min-h-[56px] max-h-[200px] resize-none bg-transparent !rounded-none !border-0 !shadow-none", |
Vercel Preview
|
Summary
Why this replaces #374
The old PR is blocked by repository code-scanning rules waiting on historical commits ( / merge commit ) that cannot be retroactively given CodeQL results. This PR rebuilds the same UI changes on top of current so GitHub can produce a fresh set of CodeQL and CI results.
Validation