Skip to content

Conversation

@leeunduck
Copy link
Owner

๐Ÿš€ Pull Request

๐Ÿ“ PR ์œ ํ˜•

  • ๊ธฐ๋Šฅ ์ถ”๊ฐ€ (Feature)
  • ๋ฒ„๊ทธ ์ˆ˜์ • (Bug Fix)
  • ์ฝ”๋“œ ๊ฐœ์„  (Refactoring)
  • ๋ฌธ์„œ ์ž‘์—… (Docs)
  • ํ™˜๊ฒฝ ์„ค์ • (Configuration)
  • ์ตœ์ข… ์ ๊ฒ€ (Release Check)

๐Ÿ” ๋ณ€๊ฒฝ ์‚ฌํ•ญ

AuthMain ๋ ˆ์ด์•„์›ƒ ์ปดํฌ๋„ŒํŠธ ์ถ”๊ฐ€
LoginForm ์ปดํฌ๋„ŒํŠธ ์ถ”๊ฐ€
Form ์ƒํƒœ๊ด€๋ฆฌ store ์ถ”๊ฐ€
Auth Header ๋ฆฌํŒฉํ† ๋ง
Input & Button variant ๋ฐ˜์‘ํ˜• ๋ฆฌํŒฉํ† ๋ง


๐Ÿ“ธ ์Šคํฌ๋ฆฐ์ƒท

แ„‰แ…ณแ„แ…ณแ„…แ…ตแ†ซแ„‰แ…ฃแ†บ 2025-11-11 23 20 55

๐Ÿšง ๊ด€๋ จ ์ด์Šˆ


๐Ÿ› ๏ธ ์ตœ์ข… ๋ฐฐํฌ ์ ๊ฒ€ ๋ฆฌ์ŠคํŠธ

  • ์ฃผ์š” ๊ธฐ๋Šฅ ๋™์ž‘ ํ™•์ธ
  • ๋นŒ๋“œ/๋ฐฐํฌ ํ™˜๊ฒฝ ์ ๊ฒ€
  • ๋ฌธ์„œ/์„ค์ • ๊ฒ€ํ† 

โœ… ์ตœ์ข… ๋ฐฐํฌ ์ ๊ฒ€ ๊ฒฐ๊ณผ

@vercel
Copy link

vercel bot commented Nov 11, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
custom-daily-planner Ready Ready Preview Comment Nov 11, 2025 2:21pm

@leeunduck leeunduck merged commit 72af2a3 into main Nov 11, 2025
8 checks passed
@leeunduck leeunduck deleted the Feature/CDP-200-LoginMain branch November 11, 2025 14:23
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

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

๐Ÿ’ก Codex Review

Here are some automated review suggestions for this pull request.

โ„น๏ธ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with ๐Ÿ‘.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +19 to +53
validateLogin: () => {
const { email, password } = get();

let emailError = false;
let passwordError = false;

// ์ด๋ฉ”์ผ: ๋น„์–ด ์žˆ๊ฑฐ๋‚˜ ํ˜•์‹์ด ์˜ฌ๋ฐ”๋ฅด์ง€ ์•Š์œผ๋ฉด ์—๋Ÿฌ
const trimmedEmail = email.trim();
const isValidEmail = /^[^\s@]+@[^\s@]+\.[^\s@]+$/.test(trimmedEmail);

if (!trimmedEmail || !isValidEmail) {
emailError = true;
}

// ๋น„๋ฐ€๋ฒˆํ˜ธ: 6์ž๋ฆฌ ์ด์ƒ + ํŠน์ˆ˜๋ฌธ์ž 1๊ฐœ ์ด์ƒ
const hasMinLength = password.length >= 6;
const hasSpecialChar = /[^A-Za-z0-9]/.test(password);

if (!hasMinLength || !hasSpecialChar) {
passwordError = true;
}

// ํ•˜๋‚˜๋ผ๋„ ์—๋Ÿฌ๊ฐ€ ์žˆ์œผ๋ฉด ํ•ด๋‹น ํ•„๋“œ ๊ฐ’ ์ดˆ๊ธฐํ™” + ์—๋Ÿฌ ํ”Œ๋ž˜๊ทธ ์„ธํŒ…
if (emailError || passwordError) {
set({
email: emailError ? "" : email,
password: passwordError ? "" : password,
emailError,
passwordError,
});
return false;
}

set({ emailError: false, passwordError: false });
return true;

Choose a reason for hiding this comment

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

P1 Badge Persist trimmed email after validation

The validator trims whitespace to check the email format but, in the success path, the store keeps the original email string (emailError remains false and no set occurs with the trimmed value). A user who types " [email protected] " will pass validation, yet the state still contains the leading/trailing spaces; any subsequent login request that reads email from the store will send the untrimmed value and likely be rejected serverโ€‘side despite the UI reporting success. Store the trimmed email when validation passes or fail validation if whitespace is present.

Useful? React with ๐Ÿ‘ย / ๐Ÿ‘Ž.

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.

2 participants