fix: remove outdated username placeholder text in login page#2519
fix: remove outdated username placeholder text in login page#2519unclamped wants to merge 1 commit intoseerr-team:developfrom
Conversation
|
No actionable comments were generated in the recent review. 🎉 📝 WalkthroughWalkthroughThe PR removes the Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 2✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
There was a problem hiding this comment.
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 | 🔴 CriticalRestore
messages.passwordto avoid aformatMessagecrash.
intl.formatMessage(messages.password)is used in the password field placeholder at line 107, but thepasswordkey is missing from thedefineMessagesobject. This leavesmessages.passwordundefined 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.
|
oh god, I didn't actually try logging in. my bad, wrong delete |
77dc037 to
437e5c9
Compare
|
You should run |
This commit also changes the data-form-type to just email instead of username
437e5c9 to
b3e42f9
Compare
| inputMode="email" | ||
| data-testid="email" | ||
| data-form-type="username,email" | ||
| data-form-type="email" |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
@fallenbagel Do you know of any tooltips I can use as reference in Seerr? This exceeds my knowledge
|
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 |
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:


Old:
Checklist:
pnpm buildpnpm i18n:extractSummary by CodeRabbit