Skip to content

fix: remove strikethrough on Client dropdown label in Work Entries page#465

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

fix: remove strikethrough on Client dropdown label in Work Entries page#465
devin-ai-integration[bot] wants to merge 1 commit intomainfrom
devin/1776164958-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

The Client dropdown in the "Add/Edit Work Entry" dialog on /work-entries had a visual bug where the outlined border passed through the "Client" label text, appearing as a strikethrough.

Root cause: MUI's Select component (outlined variant) requires a label prop matching the InputLabel text to create a notch/gap in the border for the floating label. This prop was missing.

Fix: Added label="Client" to the <Select> component, consistent with how the Reports page already handles its <Select label="Select Client">.

Before

before

After

after

Review & Testing Checklist for Human

  • Open /work-entries, click "Add Work Entry", and verify the "Client" label no longer has a line through it
  • Verify the label text "Client" on the Select matches the InputLabel text — a mismatch would cause an incorrectly sized notch

Notes

  • The same Select pattern on the Reports page (ReportsPage.tsx) already had the label prop set correctly — only WorkEntriesPage.tsx was affected.

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


Open with Devin

…own label

The MUI Select component in the Add/Edit Work Entry dialog was missing the
label prop. Without it, MUI's OutlinedInput does not create a notch in the
border for the floating InputLabel, causing the border line to pass through
the 'Client' label text and appear as a strikethrough.
@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