Skip to content

fix: add label prop to Client Select to fix strikethrough on dropdown label#469

Open
devin-ai-integration[bot] wants to merge 1 commit intomainfrom
devin/1776165098-fix-client-dropdown-strikethrough
Open

fix: add label prop to Client Select to fix strikethrough on dropdown label#469
devin-ai-integration[bot] wants to merge 1 commit intomainfrom
devin/1776165098-fix-client-dropdown-strikethrough

Conversation

@devin-ai-integration
Copy link
Copy Markdown
Contributor

@devin-ai-integration devin-ai-integration bot commented Apr 14, 2026

Summary

Fixes a UI bug on the /work-entries page where the "Client" dropdown label appeared with a strikethrough. The MUI <Select> component was missing the label="Client" prop, which is required for the outlined variant to properly cut a notch in the fieldset border for the label. Without it, the border line renders through the label text, creating a visual strikethrough.

Before: The border passes through the "Client" label text
Before

After: The notch correctly accommodates the label
After

Review & Testing Checklist for Human

  • Open the /work-entries page, click "Add Work Entry", and verify the "Client" dropdown label no longer has a strikethrough
  • Check that the notch width properly fits the "Client *" label (including the required asterisk)
  • Search for other <Select> components in the codebase that may have the same missing label prop issue (e.g., in ClientsPage.tsx, ReportsPage.tsx)

Notes

  • This is a single-line fix — standard MUI pattern where Select needs a label prop matching its InputLabel when using the outlined variant.

Link to Devin session: https://partner-workshops.devinenterprise.com/sessions/d3d2ddc6880441bfb7b3724a65d9794f


Open with Devin

… label

The MUI Select component was missing the label='Client' prop, which caused
the outlined fieldset notch to not cut through the border for the label text.
This made the border line pass through the label, creating a strikethrough effect.
@devin-ai-integration
Copy link
Copy Markdown
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

Copy link
Copy Markdown
Contributor Author

@devin-ai-integration devin-ai-integration bot left a comment

Choose a reason for hiding this comment

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

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 1 additional finding.

Open in Devin Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants