Skip to content

fix: improve UI consistency in codebase indexing popover #7041

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

roomote[bot]
Copy link

@roomote roomote bot commented Aug 13, 2025

Summary

This PR fixes the UI styling issues in the codebase indexing popover as reported in #7040.

Changes Made

  1. Added cursor pointer to collapsible headings: The Setup Settings and Advanced Settings collapsible sections now show a pointer cursor on hover, providing better visual feedback to users that these elements are clickable.

  2. Added consistent padding between labels and input fields: All input labels now have consistent bottom margin (mb-1) and are displayed as block elements, creating uniform spacing throughout the form.

Testing

  • ✅ All existing tests pass (939 tests passed, 1 skipped)
  • ✅ Linting checks pass
  • ✅ Type checking passes

Screenshots

The changes ensure:

  • Better user experience with cursor feedback on interactive elements
  • Consistent visual spacing matching the overall application style
  • Improved readability with proper label-to-input spacing

Fixes #7040


Important

Improves UI consistency in CodeIndexPopover.tsx by adding cursor feedback and consistent padding.

  • UI Enhancements:
    • Added cursor-pointer to Setup Settings and Advanced Settings buttons in CodeIndexPopover.tsx for better user feedback.
    • Ensured consistent padding by adding mb-1 and block to all label elements in CodeIndexPopover.tsx.
  • Testing:
    • All existing tests pass (939 tests passed, 1 skipped).
    • Linting and type checking pass.

This description was created by Ellipsis for 0d990f3. You can customize this summary. It will automatically update as commits are pushed.

- Add cursor-pointer class to collapsible section headers for better UX
- Add consistent padding (mb-1 block) between all labels and input fields
- Ensures visual consistency with the rest of the application styling

Fixes #7040
@roomote roomote bot requested review from mrubens, cte and jr as code owners August 13, 2025 06:59
@dosubot dosubot bot added size:M This PR changes 30-99 lines, ignoring generated files. UI/UX UI/UX related or focused labels Aug 13, 2025
Copy link
Author

@roomote roomote bot left a comment

Choose a reason for hiding this comment

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

Reviewing my own code is like debugging in a mirror - everything looks backwards but somehow still broken.

@@ -1103,7 +1103,7 @@ export const CodeIndexPopover: React.FC<CodeIndexPopoverProps> = ({
<div className="mt-4 space-y-4">
{/* Search Score Threshold Slider */}
<div className="space-y-2">
<div className="flex items-center gap-2">
<div className="flex items-center gap-2 mb-1">
Copy link
Author

Choose a reason for hiding this comment

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

I notice that here we're adding to the parent div instead of the label element itself. For consistency with all the other labels in this file (lines 616, 653, 675, 718, 749, 770, 802, 829, 857, 878, 910, 932, 975, 997, 1039, 1067), should we consider moving the classes directly to the label element?

@@ -1149,7 +1149,7 @@ export const CodeIndexPopover: React.FC<CodeIndexPopoverProps> = ({

{/* Maximum Search Results Slider */}
<div className="space-y-2">
<div className="flex items-center gap-2">
<div className="flex items-center gap-2 mb-1">
Copy link
Author

Choose a reason for hiding this comment

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

Same pattern here - for consistency with the rest of the file, the classes would typically go on the label element rather than the wrapper div.

@hannesrudolph hannesrudolph added the Issue/PR - Triage New issue. Needs quick review to confirm validity and assign labels. label Aug 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue/PR - Triage New issue. Needs quick review to confirm validity and assign labels. size:M This PR changes 30-99 lines, ignoring generated files. UI/UX UI/UX related or focused
Projects
Status: Triage
Development

Successfully merging this pull request may close these issues.

[UI] codebase indexing padding issue
2 participants