Skip to content

fix: remove outdated username placeholder text in login page#2519

Open
unclamped wants to merge 1 commit intoseerr-team:developfrom
unclamped:outdated-username-placeholder
Open

fix: remove outdated username placeholder text in login page#2519
unclamped wants to merge 1 commit intoseerr-team:developfrom
unclamped:outdated-username-placeholder

Conversation

@unclamped
Copy link

@unclamped unclamped commented Feb 19, 2026

Description

This commit removes an outdated username placeholder text for the login page. This is a reminiscent of an old migration from other media servers.
This commit also changes the data-form-type to just email instead of username. This may break some compatibility with existing password manager saves, but in my testing with Bitwarden that didn't happen (source of the claim of compatibility is GitHub Copilot)

How Has This Been Tested?

Compiled and ran through Docker compose on my local machine, an EndeavourOS host in x86_64.

Screenshots / Logs (if applicable)

New:
image
Old:
image

Checklist:

  • I have read and followed the contribution guidelines.
  • Disclosed any use of AI (see our policy)
  • [?] I have updated the documentation accordingly.
  • [?] All new and existing tests passed.
  • Successful build pnpm build
  • [?] Translation keys pnpm i18n:extract
  • Database migration (if required)

Summary by CodeRabbit

  • Improvements
    • Email input placeholder simplified to display "Email" only.
    • Login now accepts email addresses exclusively; username entry/label has been removed.

@unclamped unclamped requested a review from a team as a code owner February 19, 2026 19:59
@coderabbitai
Copy link

coderabbitai bot commented Feb 19, 2026

No actionable comments were generated in the recent review. 🎉


📝 Walkthrough

Walkthrough

The PR removes the username public message key from defineMessages in LocalLogin.tsx, updates the email input placeholder to only show email, and changes the email input's data-form-type from "username,email" to "email".

Changes

Cohort / File(s) Summary
Login messages & inputs
src/components/Login/LocalLogin.tsx
Removed username key from defineMessages; changed email input placeholder to email-only; updated email input data-form-type from "username,email" to "email".

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰
I hopped through code with carrot cheer,
Tucked “username” gently out of here.
Email now stands pure and bright,
A smaller form to feel just right. 🥕

🚥 Pre-merge checks | ✅ 2
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: removing an outdated username placeholder from the login page, which aligns with the code changes removing the 'username' key from defineMessages and updating input attributes.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
src/components/Login/LocalLogin.tsx (1)

13-23: ⚠️ Potential issue | 🔴 Critical

Restore messages.password to avoid a formatMessage crash.

intl.formatMessage(messages.password) is used in the password field placeholder at line 107, but the password key is missing from the defineMessages object. This leaves messages.password undefined and will throw at render time, breaking the login form.

✅ Suggested fix
 const messages = defineMessages('components.Login', {
   loginwithapp: 'Login with {appName}',
   username: 'Username',
   email: 'Email Address',
+  password: 'Password',
   validationemailrequired: 'You must provide a valid email address',
   validationpasswordrequired: 'You must provide a password',
   loginerror: 'Something went wrong while trying to sign in.',
   signingin: 'Signing In…',
   signin: 'Sign In',
   forgotpassword: 'Forgot Password?',
 });
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@src/components/Login/LocalLogin.tsx` around lines 13 - 23, The defineMessages
object 'messages' in LocalLogin.tsx is missing the 'password' key which causes
intl.formatMessage(messages.password) used in the password field placeholder to
crash; add a 'password' entry to the defineMessages call (alongside
loginwithapp, username, email, etc.) with an appropriate string (e.g.,
'Password') so that messages.password is defined, then ensure any tests or
usages of intl.formatMessage refer to messages.password consistently.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In `@src/components/Login/LocalLogin.tsx`:
- Around line 13-23: The defineMessages object 'messages' in LocalLogin.tsx is
missing the 'password' key which causes intl.formatMessage(messages.password)
used in the password field placeholder to crash; add a 'password' entry to the
defineMessages call (alongside loginwithapp, username, email, etc.) with an
appropriate string (e.g., 'Password') so that messages.password is defined, then
ensure any tests or usages of intl.formatMessage refer to messages.password
consistently.

@unclamped
Copy link
Author

unclamped commented Feb 19, 2026

oh god, I didn't actually try logging in. my bad, wrong delete

@unclamped unclamped force-pushed the outdated-username-placeholder branch from 77dc037 to 437e5c9 Compare February 19, 2026 20:11
@0xSysR3ll
Copy link
Contributor

You should run pnpm format before committing or CI will fail :)

This commit also changes the data-form-type to just email instead of username
@unclamped unclamped force-pushed the outdated-username-placeholder branch from 437e5c9 to b3e42f9 Compare February 19, 2026 23:02
inputMode="email"
data-testid="email"
data-form-type="username,email"
data-form-type="email"
Copy link
Collaborator

@fallenbagel fallenbagel Feb 19, 2026

Choose a reason for hiding this comment

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

This will break for jellyfin/emby users still. Normal imported users get their usernames set as their email as they do not have emails associated with their accounts. So unfortunately we cant restrict the form type.

We can remove the placeholder so its not confusing but we will need to keep this removed. And maybe add a tool tip to the field with a short way of explaining the above ^

Maybe like "if you haven't sent an email.." etc

Copy link
Author

Choose a reason for hiding this comment

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

@fallenbagel Do you know of any tooltips I can use as reference in Seerr? This exceeds my knowledge

@unclamped
Copy link
Author

sorry I completely forgot about this PR. I'm doing the changes in a few days if that's not an issue, I'm busy with exams

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.

3 participants