Skip to content

feat: Routing & Css setting#16

Merged
heeeeyong merged 19 commits intodevelopfrom
feature/signup
Jun 24, 2025
Merged

feat: Routing & Css setting#16
heeeeyong merged 19 commits intodevelopfrom
feature/signup

Conversation

@heeeeyong
Copy link
Collaborator

@heeeeyong heeeeyong commented May 26, 2025

  1. global.ts μΆ”κ°€
  2. reset.css μΆ”κ°€
  3. λΌμš°νŒ… μ„€μ •

Summary by CodeRabbit

  • μƒˆλ‘œμš΄ κΈ°λŠ₯

    • νšŒμ›κ°€μž… ν”Œλ‘œμš°μ— 닀쀑 단계 λΌμš°νŒ…μ΄ λ„μž…λ˜μ–΄ λ‹‰λ„€μž„ 및 μž₯λ₯΄ 선택 λ“± 단계별 νšŒμ›κ°€μž…μ΄ κ°€λŠ₯ν•΄μ‘ŒμŠ΅λ‹ˆλ‹€.
    • νšŒμ›κ°€μž… νŽ˜μ΄μ§€μš© 헀더 μ»΄ν¬λ„ŒνŠΈκ°€ μΆ”κ°€λ˜μ–΄ 쒌우 λ²„νŠΌκ³Ό 타이틀을 μ§€μ›ν•©λ‹ˆλ‹€.
    • κΈ€λ‘œλ²Œ μŠ€νƒ€μΌμ΄ Emotion 기반으둜 적용되며, μƒˆλ‘œμš΄ CSS 리셋이 μΆ”κ°€λ˜μ—ˆμŠ΅λ‹ˆλ‹€.
  • 버그 μˆ˜μ •

    • μ—†μŒ
  • λ¬Έμ„œν™”

    • 이슈 ν…œν”Œλ¦Ώμ— 브랜치 νƒ€μž… 선택 및 μƒμœ„ μž‘μ—… μž…λ ₯ ν•„λ“œκ°€ μΆ”κ°€λ˜κ³ , ν•„μˆ˜ μž…λ ₯으둜 λ³€κ²½λ˜μ—ˆμŠ΅λ‹ˆλ‹€.
  • λ¦¬νŒ©ν„°

    • App μ»΄ν¬λ„ŒνŠΈκ°€ κΈ€λ‘œλ²Œ μŠ€νƒ€μΌ 및 λΌμš°ν„°λ§Œ λ Œλ”λ§ν•˜λŠ” ꡬ쑰둜 λ‹¨μˆœν™”λ˜μ—ˆμŠ΅λ‹ˆλ‹€.
    • κΈ°μ‘΄ CSS νŒŒμΌλ“€μ΄ 제거되고 μŠ€νƒ€μΌ 관리가 λ³€κ²½λ˜μ—ˆμŠ΅λ‹ˆλ‹€.
  • ν™˜κ²½/μ„€μ •

    • TypeScript, CSS 및 κΈ€λ‘œλ²Œ μŠ€νƒ€μΌ κ΄€λ ¨ 섀정이 λ³€κ²½λ˜μ—ˆμŠ΅λ‹ˆλ‹€.
    • Jira μ΄μŠˆμ™€ μ—°λ™λ˜λŠ” GitHub Actions μ›Œν¬ν”Œλ‘œμš°κ°€ μΆ”κ°€ 및 μˆ˜μ •λ˜μ—ˆμŠ΅λ‹ˆλ‹€.

@heeeeyong heeeeyong added the 🎨 Html&css λ§ˆν¬μ—… & μŠ€νƒ€μΌλ§ label May 26, 2025
@heeeeyong heeeeyong changed the title [Chore] Css setting [feat] λΌμš°νŒ… & Css setting May 27, 2025
@heeeeyong heeeeyong added the ✨ Feature κΈ°λŠ₯ 개발 label May 27, 2025
@heeeeyong heeeeyong changed the title [feat] λΌμš°νŒ… & Css setting [feat] Routing & Css setting May 27, 2025
@heeeeyong
Copy link
Collaborator Author

@coderabbitai review

@coderabbitai
Copy link

coderabbitai bot commented Jun 22, 2025

βœ… Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@coderabbitai
Copy link

coderabbitai bot commented Jun 22, 2025

Walkthrough

이번 λ³€κ²½μ—μ„œλŠ” GitHub 이슈 ν…œν”Œλ¦Ώ 및 μ›Œν¬ν”Œλ‘œμš°μ˜ κ°œμ„ , μ „μ—­ μŠ€νƒ€μΌλ§ μ²΄κ³„μ˜ 개편, λΌμš°νŒ… ꡬ쑰 λ„μž…, 그리고 κΈ°μ‘΄ CSS 파일의 정리 및 Emotion 기반 κΈ€λ‘œλ²Œ μŠ€νƒ€μΌ 적용이 μ΄λ£¨μ–΄μ‘ŒμŠ΅λ‹ˆλ‹€. λ˜ν•œ TypeScript 섀정이 Emotionκ³Ό ν˜Έν™˜λ˜λ„λ‘ μˆ˜μ •λ˜μ—ˆμŠ΅λ‹ˆλ‹€.

Changes

파일/경둜 λ³€κ²½ μš”μ•½
.github/ISSUE_TEMPLATE/issue_form.yml μƒμœ„ μž‘μ—… ν•„λ“œ ν”Œλ ˆμ΄μŠ€ν™€λ” λ³€κ²½ 및 ν•„μˆ˜ν™”, 브랜치 νƒ€μž… λ“œλ‘­λ‹€μš΄ ν•„λ“œ μΆ”κ°€
.github/workflows/close-jira-issue.yml 이슈 μ’…λ£Œ μ‹œ Jira 이슈λ₯Ό "μ™„λ£Œ"둜 μ „ν™˜ν•˜λŠ” μƒˆ GitHub Actions μ›Œν¬ν”Œλ‘œμš° μΆ”κ°€
.github/workflows/create-jira-issue.yml 이슈 ν…œν”Œλ¦Ώ 경둜 μˆ˜μ •, Jira ν”„λ‘œμ νŠΈ ν‚€ λ³€κ²½, 브랜치 생성 단계 전체 주석 처리, 타이틀 처리 방식 일뢀 λ³€κ²½
src/App.css
src/index.css
κΈ°μ‘΄ CSS μŠ€νƒ€μΌ 파일 전체 μ‚­μ œ
src/reset.css HTML μš”μ†Œμ˜ κΈ°λ³Έ μŠ€νƒ€μΌμ„ μ΄ˆκΈ°ν™”ν•˜λŠ” CSS reset 파일 μ‹ κ·œ μΆ”κ°€
src/main.css reset.css import μΆ”κ°€
src/main.tsx index.css importλ₯Ό main.css import둜 λ³€κ²½
src/App.tsx μƒνƒœμ™€ UIλ₯Ό μ œκ±°ν•˜κ³  κΈ€λ‘œλ²Œ μŠ€νƒ€μΌ 및 Router만 λ°˜ν™˜ν•˜λŠ” ν•¨μˆ˜ν˜• μ»΄ν¬λ„ŒνŠΈλ‘œ μ „λ©΄ λ¦¬νŒ©ν† λ§
src/pages/index.tsx react-router-dom 기반의 λΌμš°ν„° 및 νšŒμ›κ°€μž… 단계별 λΌμš°νŒ… ꡬ쑰 μ‹ κ·œ λ„μž…, Router μ»΄ν¬λ„ŒνŠΈ export
src/styles/global/global.ts Emotion을 ν™œμš©ν•œ κΈ€λ‘œλ²Œ μŠ€νƒ€μΌ μ •μ˜ 및 export
tsconfig.app.json Emotion JSX μžλ™ μž„ν¬νŠΈ μ„€μ •(jsxImportSource) μΆ”κ°€
src/pages/signup/Header.tsx νšŒμ›κ°€μž… νŽ˜μ΄μ§€μš© κ³ μ • 헀더 μ»΄ν¬λ„ŒνŠΈ μ‹ κ·œ μΆ”κ°€
src/pages/signup/Signup.styled.ts νšŒμ›κ°€μž… νŽ˜μ΄μ§€ μŠ€νƒ€μΌμš© Emotion styled μ»΄ν¬λ„ŒνŠΈλ“€ μ‹ κ·œ μΆ”κ°€
src/pages/signup/Signup.tsx νšŒμ›κ°€μž… λΌμš°νŒ…μš© Outlet 포함 μ»΄ν¬λ„ŒνŠΈ μ‹ κ·œ μΆ”κ°€
src/pages/signup/SignupGenre.tsx νšŒμ›κ°€μž… μž₯λ₯΄ 선택 단계 μ»΄ν¬λ„ŒνŠΈ μ‹ κ·œ μΆ”κ°€
src/pages/signup/SignupNickname.tsx νšŒμ›κ°€μž… λ‹‰λ„€μž„ μž…λ ₯ 단계 μ»΄ν¬λ„ŒνŠΈ μ‹ κ·œ μΆ”κ°€

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant GitHub Issue
    participant GitHub Actions
    participant Jira

    User->>GitHub Issue: 이슈 생성 및 μ’…λ£Œ
    GitHub Issue-->>GitHub Actions: 이슈 μ’…λ£Œ 이벀트 λ°œμƒ
    GitHub Actions->>Jira: Jira 둜그인 (Secrets μ‚¬μš©)
    GitHub Actions->>GitHub Issue: 이슈 νƒ€μ΄ν‹€μ—μ„œ Jira ν‚€ μΆ”μΆœ
    alt Jira ν‚€ 있음
        GitHub Actions->>Jira: ν•΄λ‹Ή 이슈λ₯Ό "μ™„λ£Œ"둜 μƒνƒœ μ „ν™˜
    else Jira ν‚€ μ—†μŒ
        GitHub Actions-->>GitHub Actions: μ—λŸ¬ 및 μ›Œν¬ν”Œλ‘œμš° μ’…λ£Œ
    end
Loading
sequenceDiagram
    participant User
    participant App
    participant Router
    participant Signup
    participant SignupNickname
    participant SignupGenre

    User->>App: 접속
    App->>Router: λ Œλ”λ§
    Router->>Signup: "signup" 경둜 μ§„μž…
    Signup->>SignupNickname: κΈ°λ³Έ(index) 경둜 μ§„μž…
    User->>Router: "signup/genre" 경둜 이동
    Router->>SignupGenre: "signup/genre" μ§„μž…
Loading

Poem

🐰
μŠ€νƒ€μΌμ΄ λ°”λ€Œκ³ , λΌμš°ν„°κ°€ μƒˆλ‘œμ›Œμ‘Œλ„€
CSSλŠ” μ •λ¦¬ν•˜κ³ , Emotion이 반짝!
이슈 λ‹«μœΌλ©΄ Jira도 μ²™μ²™
브랜치 νƒ€μž… κ³ λ₯΄κ³ , ν…œν”Œλ¦Ώλ„ 깔끔
ν† λΌλŠ” μ˜€λŠ˜λ„ μ½”λ“œλ°­μ—μ„œ 깑총!

✨ Finishing Touches
  • πŸ“ Generate Docstrings

πŸͺ§ Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

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.

Actionable comments posted: 1

🧹 Nitpick comments (3)
src/styles/global/global.ts (1)

4-6: 폰트 νŒ¨λ°€λ¦¬ λŒ€μ²΄ κΈ€κΌ΄ μΆ”κ°€ μ œμ•ˆ
ν˜„μž¬ Pretendard Variable만 μ„ μ–Έλ˜μ–΄ μžˆμ–΄ λ‘œλ”© μ‹€νŒ¨ μ‹œ 폴백이 μ—†μŠ΅λ‹ˆλ‹€. μ‹œμŠ€ν…œ κΈ°λ³Έ ν°νŠΈλ‚˜ sans-serifλ₯Ό ν•¨κ»˜ μ§€μ •ν•˜λŠ” 것을 ꢌμž₯ν•©λ‹ˆλ‹€.

* {
-  font-family: Pretendard Variable;
+  font-family: 'Pretendard Variable', system-ui, sans-serif;
}
src/pages/index.tsx (1)

14-19: λΆˆν•„μš”ν•œ Fragmentλ₯Ό μ œκ±°ν•˜μ„Έμš”.

정적 뢄석 λ„κ΅¬μ˜ 지적이 μ •ν™•ν•©λ‹ˆλ‹€. createRoutesFromElementsλŠ” 직접 Route μš”μ†Œλ“€μ„ 받을 수 μžˆμœΌλ―€λ‘œ Fragment λž˜νΌκ°€ ν•„μš”ν•˜μ§€ μ•ŠμŠ΅λ‹ˆλ‹€.

λ‹€μŒκ³Ό 같이 μˆ˜μ •ν•˜μ„Έμš”:

  const router = createBrowserRouter(
    createRoutesFromElements(
-      <>
-        <Route path="signup" element={<Signup />}>
-          <Route index element={<SignupNickname />} />
-          <Route path="second" element={<SignupGenre />} />
-        </Route>
-      </>,
+      <Route path="signup" element={<Signup />}>
+        <Route index element={<SignupNickname />} />
+        <Route path="second" element={<SignupGenre />} />
+      </Route>
    ),
  );
.github/workflows/create-jira-issue.yml (1)

69-76: λ―Έμ‚¬μš© 브랜치 생성 μŠ€ν… 주석 정리 μ œμ•ˆ

브랜치 생성 둜직이 주석 μ²˜λ¦¬λ˜μ–΄ μžˆλŠ”λ°, μΆ”ν›„ μ‚¬μš© κ³„νšμ΄ μ—†λ‹€λ©΄ μ‚­μ œν•˜κ±°λ‚˜ 주석 이유λ₯Ό 주석 상단에 κ°„λ‹¨νžˆ λͺ…μ‹œν•˜λ©΄ μœ μ§€λ³΄μˆ˜κ°€ μš©μ΄ν•©λ‹ˆλ‹€.

πŸ“œ Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between d74a4c6 and 33eb0a5.

πŸ“’ Files selected for processing (12)
  • .github/ISSUE_TEMPLATE/issue_form.yml (1 hunks)
  • .github/workflows/close-jira-issue.yml (1 hunks)
  • .github/workflows/create-jira-issue.yml (3 hunks)
  • src/App.css (0 hunks)
  • src/App.tsx (1 hunks)
  • src/index.css (0 hunks)
  • src/main.css (1 hunks)
  • src/main.tsx (1 hunks)
  • src/pages/index.tsx (1 hunks)
  • src/reset.css (1 hunks)
  • src/styles/global/global.ts (1 hunks)
  • tsconfig.app.json (1 hunks)
πŸ’€ Files with no reviewable changes (2)
  • src/App.css
  • src/index.css
🧰 Additional context used
🧬 Code Graph Analysis (1)
src/App.tsx (1)
src/styles/global/global.ts (1)
  • globalStyles (3-10)
πŸͺ› Biome (1.9.4)
tsconfig.app.json

[error] 21-21: End of file expected

Use an array for a sequence of values: [1, 2]

(parse)


[error] 21-21: End of file expected

Use an array for a sequence of values: [1, 2]

(parse)


[error] 21-21: End of file expected

Use an array for a sequence of values: [1, 2]

(parse)


[error] 21-23: End of file expected

Use an array for a sequence of values: [1, 2]

(parse)

src/reset.css

[error] 86-86: Unexpected shorthand property font after font-size

(lint/suspicious/noShorthandPropertyOverrides)

src/pages/index.tsx

[error] 14-19: Avoid using unnecessary Fragment.

A fragment is redundant if it contains only one child, or if it is the child of a html element, and is not a keyed fragment.
Unsafe fix: Remove the Fragment

(lint/complexity/noUselessFragments)

πŸͺ› actionlint (1.7.7)
.github/workflows/close-jira-issue.yml

22-22: "github.event.issue.title" is potentially untrusted. avoid using it directly in inline scripts. instead, pass it through an environment variable. see https://docs.github.com/en/actions/security-for-github-actions/security-guides/security-hardening-for-github-actions for more details

(expression)

πŸ”‡ Additional comments (17)
src/reset.css (2)

1-124: 리셋 CSS μΆ”κ°€ 승인
μ „λ²”μœ„ HTML μš”μ†Œμ— λŒ€ν•œ λ§ˆμ§„Β·νŒ¨λ”©Β·ν…Œλ‘λ¦¬ 제거, HTML5 μ‹œλ§¨ν‹± μ—˜λ¦¬λ¨ΌνŠΈ display μ„€μ •, λ¦¬μŠ€νŠΈΒ·ν…Œμ΄λΈ”Β·μΈμš©λ¬Έ 리셋이 μ˜¬λ°”λ₯΄κ²Œ μ μš©λ˜μ—ˆμŠ΅λ‹ˆλ‹€.


85-86: static analysis κ²½κ³  λ¬΄μ‹œ
font-size: 100% 뒀에 font: inherit을 μ„ μ–Έν•˜λŠ” 것은 CSS 리셋 νŒ¨ν„΄μ˜ ν‘œμ€€μ΄λ―€λ‘œ biome λ„κ΅¬μ˜ β€œnoShorthandPropertyOverrides” κ²½κ³ λŠ” false positiveμž…λ‹ˆλ‹€.

src/main.css (1)

1-1: 리셋 CSS μž„ν¬νŠΈ 확인
reset.cssλ₯Ό μ΅œμƒλ‹¨μ— μž„ν¬νŠΈν•˜μ—¬ 리셋 μŠ€νƒ€μΌμ΄ λ‹€λ₯Έ μŠ€νƒ€μΌλ³΄λ‹€ μš°μ„  μ μš©λ˜λ„λ‘ 잘 κ΅¬μ„±λ˜μ—ˆμŠ΅λ‹ˆλ‹€.

src/main.tsx (1)

3-3: κΈ€λ‘œλ²Œ CSS 경둜 μ—…λ°μ΄νŠΈ 승인
κΈ°μ‘΄ index.css λŒ€μ‹  main.cssλ₯Ό μ˜¬λ°”λ₯΄κ²Œ λ‘œλ“œν•˜λ„λ‘ import 문이 μ—…λ°μ΄νŠΈλ˜μ—ˆμŠ΅λ‹ˆλ‹€.

tsconfig.app.json (1)

21-21: Emotion JSX λŸ°νƒ€μž„ μ„€μ • μΆ”κ°€ 승인
"jsxImportSource": "@emotion/react" μ˜΅μ…˜μ„ 톡해 Emotion μžλ™ JSX λŸ°νƒ€μž„μ΄ ν™œμ„±ν™”λ˜μ—ˆμŠ΅λ‹ˆλ‹€.

src/styles/global/global.ts (1)

3-10: κΈ€λ‘œλ²Œ μŠ€νƒ€μΌ μ •μ˜ 확인
Emotion cssλ₯Ό μ΄μš©ν•΄ λͺ¨λ“  μš”μ†Œμ— box-sizing: border-box와 κΈ°λ³Έ 폰트 μŠ€νƒ€μΌμ„ μΌκ΄€λ˜κ²Œ μ μš©ν–ˆμŠ΅λ‹ˆλ‹€.

src/pages/index.tsx (1)

11-25: λΌμš°νŒ… ꡬ쑰가 잘 μ„€κ³„λ˜μ—ˆμŠ΅λ‹ˆλ‹€.

λ©€ν‹°μŠ€ν… νšŒμ›κ°€μž… ν”Œλ‘œμš°λ₯Ό μœ„ν•œ 쀑첩 λΌμš°νŒ… ꡬ쑰가 λ…Όλ¦¬μ μœΌλ‘œ 잘 κ΅¬μ„±λ˜μ–΄ μžˆμŠ΅λ‹ˆλ‹€. 메인 "signup" 경둜 ν•˜μœ„μ— λ‹‰λ„€μž„ μ„€μ •(index)κ³Ό μž₯λ₯΄ 선택(second) 단계가 λͺ…ν™•ν•˜κ²Œ λΆ„λ¦¬λ˜μ–΄ μžˆμŠ΅λ‹ˆλ‹€.

src/App.tsx (2)

1-3: Import ꡬ쑰가 κΉ”λ”ν•˜κ²Œ μ •λ¦¬λ˜μ—ˆμŠ΅λ‹ˆλ‹€.

ν•„μš”ν•œ μ˜μ‘΄μ„±λ“€λ§Œ μž„ν¬νŠΈν•˜μ—¬ μ½”λ“œκ°€ κ°„κ²°ν•΄μ‘ŒμŠ΅λ‹ˆλ‹€. Router, Emotion Global μ»΄ν¬λ„ŒνŠΈ, 그리고 κΈ€λ‘œλ²Œ μŠ€νƒ€μΌμ΄ λͺ…ν™•ν•˜κ²Œ λΆ„λ¦¬λ˜μ–΄ μžˆμŠ΅λ‹ˆλ‹€.


5-12: App μ»΄ν¬λ„ŒνŠΈ λ¦¬νŒ©ν† λ§μ΄ ν›Œλ₯­ν•©λ‹ˆλ‹€.

기쑴의 λ³΅μž‘ν•œ μƒνƒœκ΄€λ¦¬μ™€ UI λ‘œμ§μ„ μ œκ±°ν•˜κ³  κ΄€μ‹¬μ‚¬μ˜ 뢄리 원칙에 따라 App μ»΄ν¬λ„ŒνŠΈλ₯Ό λ‹€μŒκ³Ό 같이 역할을 λͺ…ν™•νžˆ ν–ˆμŠ΅λ‹ˆλ‹€:

  • κΈ€λ‘œλ²Œ μŠ€νƒ€μΌ 적용 (Emotion Global μ»΄ν¬λ„ŒνŠΈ μ‚¬μš©)
  • λΌμš°νŒ… 제곡 (Router μ»΄ν¬λ„ŒνŠΈ 톡합)

μ΄λŸ¬ν•œ κ΅¬μ‘°λŠ” μœ μ§€λ³΄μˆ˜μ„±κ³Ό 가독성을 크게 ν–₯μƒμ‹œν‚΅λ‹ˆλ‹€.

.github/ISSUE_TEMPLATE/issue_form.yml (2)

11-13: Ticket 번호 μž…λ ₯ ν•„λ“œ placeholder 및 ν•„μˆ˜ 검증 μΆ”κ°€ 확인 μš”μ²­

parentKey ν•„λ“œμ˜ placeholderλ₯Ό THIP2025-00둜 λ³€κ²½ν•˜κ³  validations.required: trueλ₯Ό μΆ”κ°€ν•œ 것은 Jira 포맷 일관성 확보에 도움이 λ©λ‹ˆλ‹€.
μ›Œν¬ν”Œλ‘œμš°(create-jira-issue.yml λ“±)μ—μ„œ ν•΄λ‹Ή ν•„λ“œκ°€ μ˜¬λ°”λ₯΄κ²Œ νŒŒμ‹±λ˜λŠ”μ§€ 검증해 μ£Όμ„Έμš”.


15-23: 브랜치 νƒ€μž… λ“œλ‘­λ‹€μš΄ ν•„λ“œ μΆ”κ°€ κ²€ν† 

branchType λ“œλ‘­λ‹€μš΄μ„ μ‹ κ·œλ‘œ λ„μž…ν•΄ feature/bugfix/hotfix/refactor μ˜΅μ…˜μ„ μ§€μ •ν•˜μ…¨μŠ΅λ‹ˆλ‹€.
Issue Parser(stefanbuck/github-issue-praser)μ—μ„œ issueparser_branchType둜 μ •ν™•νžˆ λ§€ν•‘λ˜λŠ”μ§€ 확인이 ν•„μš”ν•©λ‹ˆλ‹€.

.github/workflows/create-jira-issue.yml (3)

27-28: ν…œν”Œλ¦Ώ 경둜 일치 확인

template-pathλ₯Ό .github/ISSUE_TEMPLATE/issue_form.yml둜 μ—…λ°μ΄νŠΈν•˜μ…¨μŠ΅λ‹ˆλ‹€.
파일λͺ…(issue_form.yml)이 리포지토리에 μ •ν™•νžˆ μ‘΄μž¬ν•˜λŠ”μ§€, κΈ°μ‘΄ 경둜(issue-form.yml) μ°Έμ‘°κ°€ λ‚¨μ•„μžˆλŠ”μ§€ 점검해 μ£Όμ„Έμš”.


50-50: ν”„λ‘œμ νŠΈ ν‚€ μ—…λ°μ΄νŠΈ 승인

Jira ν”„λ‘œμ νŠΈ ν‚€λ₯Ό SKPμ—μ„œ THIP2025둜 λ³€κ²½ν•˜μ‹  것은 이슈 폼과 μΌκ΄€λ©λ‹ˆλ‹€.


83-84: 이슈 제λͺ© 포맷 검증 μš”μ²­

이전 μ»€λ°‹μ—μ„œ Jira ν‚€λ₯Ό μ œμ™Έν•˜κ³  GitHub 이슈 제λͺ©λ§Œ μ‚¬μš©ν•˜λ„λ‘ λ³€κ²½ν•˜μ…¨μŠ΅λ‹ˆλ‹€.
Jira 이슈 링크 생성 μ‹œ ν‚€ λ…ΈμΆœμ΄ ν•„μš”ν•œμ§€ μ—¬λΆ€(예: νŒ€ ν•©μ˜λœ μ»¨λ²€μ…˜)λ₯Ό μž¬ν™•μΈν•΄ μ£Όμ„Έμš”.

.github/workflows/close-jira-issue.yml (3)

27-28: Jira ν‚€ μΆ”μΆœ μ •κ·œμ‹ 검증 μš”μ²­

grep -oE '[A-Z0-9]+-[0-9]+' νŒ¨ν„΄μ΄ λͺ¨λ“  ν”„λ‘œμ νŠΈ ν‚€(영문 λŒ€λ¬Έμž+숫자)와 이슈 번호 쑰합을 ν¬κ΄„ν•˜λŠ”μ§€ 확인해 μ£Όμ„Έμš”. ν•„μš” μ‹œ μ†Œλ¬Έμž λ˜λŠ” μΆ”κ°€ 포맷을 μ§€μ›ν•˜λ„λ‘ ν™•μž₯ κ²€ν† κ°€ ν•„μš”ν•©λ‹ˆλ‹€.


29-32: 이슈 ν‚€ 미발견 μ‹œ 였λ₯˜ 처리 적절

Jira ν‚€κ°€ μΆ”μΆœλ˜μ§€ μ•Šμ„ 경우 μ¦‰μ‹œ μ’…λ£Œ(exit 1)ν•˜λ„λ‘ κ΅¬ν˜„λœ 점이 μ μ ˆν•©λ‹ˆλ‹€.


37-41: 이슈 μƒνƒœ μ „ν™˜ μŠ€ν… 확인 μš”μ²­

atlassian/gajira-transition@v3둜 "μ™„λ£Œ" μƒνƒœλ‘œ μ „ν™˜ν•˜λ„λ‘ μ„€μ •ν•˜μ…¨μŠ΅λ‹ˆλ‹€.
Jira μ›Œν¬ν”Œλ‘œμš°μ—μ„œ transition 이름이 μ •ν™•νžˆ "μ™„λ£Œ"인지 확인해 μ£Όμ„Έμš”.

Comment on lines +23 to +26
ISSUE_TITLE="${{ github.event.issue.title }}"
CLEANED_TITLE=$(echo "$ISSUE_TITLE" | tr -d '[]')
echo "🧼 Cleaned title: $CLEANED_TITLE"

Copy link

Choose a reason for hiding this comment

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

πŸ› οΈ Refactor suggestion

λ³΄μ•ˆ: 인라인 μŠ€ν¬λ¦½νŠΈμ—μ„œ GitHub 이벀트 λ³€μˆ˜ 직접 μ‚¬μš© κΈˆμ§€

ν˜„μž¬ μŠ€ν¬λ¦½νŠΈμ—μ„œ ${{ github.event.issue.title }}λ₯Ό 직접 μ‚½μž…ν•΄ μž…λ ₯값을 μ²˜λ¦¬ν•˜κ³  μžˆμ–΄ μ½”λ“œ μΈμ μ…˜ μœ„ν—˜μ΄ μžˆμŠ΅λ‹ˆλ‹€.
ν™˜κ²½ λ³€μˆ˜λ‘œ μ „λ‹¬ν•˜λ„λ‘ μ•„λž˜ μ˜ˆμ‹œμ™€ 같이 λ¦¬νŒ©ν† λ§μ„ ꢌμž₯ν•©λ‹ˆλ‹€:

- run: |
-   ISSUE_TITLE="${{ github.event.issue.title }}"
-   CLEANED_TITLE=$(echo "$ISSUE_TITLE" | tr -d '[]')
+ env:
+   ISSUE_TITLE: ${{ github.event.issue.title }}
+ run: |
+   CLEANED_TITLE=$(echo "$ISSUE_TITLE" | tr -d '[]')
πŸ“ Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
ISSUE_TITLE="${{ github.event.issue.title }}"
CLEANED_TITLE=$(echo "$ISSUE_TITLE" | tr -d '[]')
echo "🧼 Cleaned title: $CLEANED_TITLE"
env:
ISSUE_TITLE: ${{ github.event.issue.title }}
run: |
CLEANED_TITLE=$(echo "$ISSUE_TITLE" | tr -d '[]')
echo "🧼 Cleaned title: $CLEANED_TITLE"
πŸ€– Prompt for AI Agents
In .github/workflows/close-jira-issue.yml around lines 23 to 26, avoid directly
using the GitHub event variable `${{ github.event.issue.title }}` inside the
inline script to prevent code injection risks. Instead, pass the issue title as
an environment variable to the script step, then reference that environment
variable within the script. Refactor the workflow to set ISSUE_TITLE as an env
variable and use it safely inside the script without direct interpolation.

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.

Actionable comments posted: 3

🧹 Nitpick comments (4)
src/pages/index.tsx (1)

11-25: λΌμš°νŒ… ꡬ쑰 κ°œμ„  μ œμ•ˆ

ν˜„μž¬ λΌμš°ν„° ꡬ성은 기본적으둜 μ˜¬λ°”λ₯΄μ§€λ§Œ, μ‚¬μš©μž κ²½ν—˜ κ°œμ„ μ„ μœ„ν•œ λͺ‡ κ°€μ§€ 고렀사항이 μžˆμŠ΅λ‹ˆλ‹€.

λ‹€μŒ κ°œμ„ μ‚¬ν•­λ“€μ„ κ³ λ €ν•΄λ³΄μ„Έμš”:

  1. μ—λŸ¬ λ°”μš΄λ”λ¦¬ 및 404 처리 μΆ”κ°€:
<Route path="signup" element={<Signup />}>
  <Route index element={<SignupNickname />} />
  <Route path="genre" element={<SignupGenre />} />
</Route>
<Route path="*" element={<NotFound />} />
  1. 루트 경둜 λ¦¬λ‹€μ΄λ ‰μ…˜:
<Route path="/" element={<Navigate to="/signup" replace />} />
src/pages/signup/SignupNickname.tsx (2)

17-20: λΌμš°νŒ… 경둜 μƒμˆ˜ν™” κ³ λ €

ν•˜λ“œμ½”λ”©λœ 경둜 λ¬Έμžμ—΄μ€ μœ μ§€λ³΄μˆ˜ μ‹œ μ˜€νƒ€λ‚˜ 일관성 문제λ₯Ό μ•ΌκΈ°ν•  수 μžˆμŠ΅λ‹ˆλ‹€.

λΌμš°νŒ… 경둜λ₯Ό μƒμˆ˜λ‘œ κ΄€λ¦¬ν•˜λŠ” 것을 κ³ λ €ν•΄λ³΄μ„Έμš”:

// constants/routes.ts
export const ROUTES = {
  SIGNUP: '/signup',
  SIGNUP_GENRE: '/signup/genre',
} as const;

// μ»΄ν¬λ„ŒνŠΈμ—μ„œ μ‚¬μš©
const handleNextClick = () => {
  if (!isNextActive) return;
  navigate(ROUTES.SIGNUP_GENRE);
};

11-11: 검증 둜직 λͺ…ν™•μ„± κ°œμ„ 

쑰건뢀 ν™œμ„±ν™” 둜직이 λͺ…ν™•ν•˜μ§€λ§Œ, 가독성을 μœ„ν•΄ ν•¨μˆ˜λ‘œ λΆ„λ¦¬ν•˜κ±°λ‚˜ 주석을 μΆ”κ°€ν•˜λŠ” 것이 μ’‹κ² μŠ΅λ‹ˆλ‹€.

// λ‹‰λ„€μž„ μœ νš¨μ„± 검사: 2-10자 λ²”μœ„
const isValidNickname = (nickname: string) => 
  nickname.length >= 2 && nickname.length <= maxLength;

const isNextActive = isValidNickname(nickname);
src/pages/signup/SignupGenre.tsx (1)

26-30: μž₯λ₯΄ 선택 κΈ°λŠ₯ λ―Έκ΅¬ν˜„

ν˜„μž¬ μž₯λ₯΄ 선택을 μ•ˆλ‚΄ν•˜λŠ” ν…μŠ€νŠΈλ§Œ 있고, μ‹€μ œ 선택할 수 μžˆλŠ” UIλ‚˜ μƒνƒœ 관리가 κ΅¬ν˜„λ˜μ–΄ μžˆμ§€ μ•ŠμŠ΅λ‹ˆλ‹€.

μž₯λ₯΄ 선택 κΈ°λŠ₯ κ΅¬ν˜„μ΄ ν•„μš”ν•©λ‹ˆλ‹€. λ‹€μŒκ³Ό 같은 κΈ°λŠ₯듀을 κ΅¬ν˜„ν•΄μ•Ό ν•©λ‹ˆλ‹€:

  1. μž₯λ₯΄ λͺ©λ‘ 데이터
  2. 선택 μƒνƒœ 관리
  3. 선택 UI (μ²΄ν¬λ°•μŠ€, λΌλ””μ˜€ λ²„νŠΌ λ“±)
  4. 선택 검증 둜직

이 κΈ°λŠ₯듀을 κ΅¬ν˜„ν•˜λŠ” μ½”λ“œλ₯Ό μƒμ„±ν•΄λ“œλ¦΄κΉŒμš”?

πŸ“œ Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between 33eb0a5 and 8efc489.

β›” Files ignored due to path filters (2)
  • src/assets/leftArrow.svg is excluded by !**/*.svg
  • src/assets/react.svg is excluded by !**/*.svg
πŸ“’ Files selected for processing (7)
  • src/pages/index.tsx (1 hunks)
  • src/pages/signup/Header.tsx (1 hunks)
  • src/pages/signup/Signup.styled.ts (1 hunks)
  • src/pages/signup/Signup.tsx (1 hunks)
  • src/pages/signup/SignupGenre.tsx (1 hunks)
  • src/pages/signup/SignupNickname.tsx (1 hunks)
  • src/styles/global/global.ts (1 hunks)
βœ… Files skipped from review due to trivial changes (3)
  • src/pages/signup/Signup.tsx
  • src/pages/signup/Header.tsx
  • src/pages/signup/Signup.styled.ts
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/styles/global/global.ts
🧰 Additional context used
🧬 Code Graph Analysis (2)
src/pages/signup/SignupNickname.tsx (1)
src/pages/signup/Signup.styled.ts (4)
  • Container (3-36)
  • InputBox (38-50)
  • StyledInput (52-66)
  • CharCount (68-76)
src/pages/signup/SignupGenre.tsx (1)
src/pages/signup/Signup.styled.ts (1)
  • Container (3-36)
πŸͺ› Biome (1.9.4)
src/pages/index.tsx

[error] 14-19: Avoid using unnecessary Fragment.

A fragment is redundant if it contains only one child, or if it is the child of a html element, and is not a keyed fragment.
Unsafe fix: Remove the Fragment

(lint/complexity/noUselessFragments)

πŸ”‡ Additional comments (1)
src/pages/signup/SignupGenre.tsx (1)

4-4: μ•„μ΄μ½˜ μ‚¬μš© νŒ¨ν„΄ μž¬ν™•μΈμ„ μœ„ν•΄ .tsx 파일만 λŒ€μƒμœΌλ‘œ λ‹€μŒ 슀크립트λ₯Ό μ‹€ν–‰ν•΄μ£Όμ„Έμš”:

#!/bin/bash
# .tsx νŒŒμΌμ—μ„œ SVG import 및 leftArrow ν‚€μ›Œλ“œ 검색
rg -A 3 -B 1 "import .*\.svg" --glob "*.tsx"
rg -A 3 -B 1 "leftarrow|leftArrow" --glob "*.tsx"

Comment on lines +14 to +19
<>
<Route path="signup" element={<Signup />}>
<Route index element={<SignupNickname />} />
<Route path="genre" element={<SignupGenre />} />
</Route>
</>,
Copy link

Choose a reason for hiding this comment

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

πŸ› οΈ Refactor suggestion

λΆˆν•„μš”ν•œ Fragment 제거

정적 뢄석 도ꡬ가 μ§€μ ν•œ λŒ€λ‘œ, 단일 μžμ‹ μš”μ†Œλ§Œ ν¬ν•¨ν•˜λŠ” FragmentλŠ” λΆˆν•„μš”ν•©λ‹ˆλ‹€.

λ‹€μŒκ³Ό 같이 μˆ˜μ •ν•˜μ„Έμš”:

-      <>
-        <Route path="signup" element={<Signup />}>
-          <Route index element={<SignupNickname />} />
-          <Route path="genre" element={<SignupGenre />} />
-        </Route>
-      </>,
+      <Route path="signup" element={<Signup />}>
+        <Route index element={<SignupNickname />} />
+        <Route path="genre" element={<SignupGenre />} />
+      </Route>,
πŸ“ Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<>
<Route path="signup" element={<Signup />}>
<Route index element={<SignupNickname />} />
<Route path="genre" element={<SignupGenre />} />
</Route>
</>,
<Route path="signup" element={<Signup />}>
<Route index element={<SignupNickname />} />
<Route path="genre" element={<SignupGenre />} />
</Route>,
🧰 Tools
πŸͺ› Biome (1.9.4)

[error] 14-19: Avoid using unnecessary Fragment.

A fragment is redundant if it contains only one child, or if it is the child of a html element, and is not a keyed fragment.
Unsafe fix: Remove the Fragment

(lint/complexity/noUselessFragments)

πŸ€– Prompt for AI Agents
In src/pages/index.tsx around lines 14 to 19, remove the unnecessary React
Fragment wrapping the single Route element, as it only contains one child.
Replace the fragment with just the Route component directly to simplify the JSX
structure.

Comment on lines +22 to +24
const handleInputChange = (e: React.ChangeEvent<HTMLInputElement>) => {
setNickname(e.target.value);
};
Copy link

Choose a reason for hiding this comment

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

πŸ› οΈ Refactor suggestion

μž…λ ₯ 검증 κ°•ν™” μ œμ•ˆ

ν˜„μž¬ 길이만 κ²€μ¦ν•˜κ³  μžˆμ§€λ§Œ, ν”Œλ ˆμ΄μŠ€ν™€λ”μ—μ„œ μ–ΈκΈ‰ν•œ "ν•œκΈ€/μ˜μ–΄/숫자" μ œν•œμ„ μ‹€μ œλ‘œ κ΅¬ν˜„ν•˜μ§€ μ•Šμ•˜μŠ΅λ‹ˆλ‹€.

μž…λ ₯ 값을 κ²€μ¦ν•˜λŠ” λ‘œμ§μ„ μΆ”κ°€ν•΄λ³΄μ„Έμš”:

const handleInputChange = (e: React.ChangeEvent<HTMLInputElement>) => {
  const value = e.target.value;
  // ν•œκΈ€, μ˜μ–΄, 숫자만 ν—ˆμš©ν•˜λŠ” μ •κ·œμ‹
  const regex = /^[κ°€-힣a-zA-Z0-9]*$/;
  
  if (value === '' || regex.test(value)) {
    setNickname(value);
  }
};
πŸ€– Prompt for AI Agents
In src/pages/signup/SignupNickname.tsx around lines 22 to 24, the input change
handler currently only updates the nickname state without validating the input
against allowed characters. To fix this, add a validation step using a regular
expression that permits only Korean characters, English letters, and numbers.
Update the handler to check if the input is either empty or matches the regex
/^[κ°€-힣a-zA-Z0-9]*$/ before calling setNickname, ensuring the nickname respects
the placeholder's character restrictions.

Comment on lines +13 to +15
const handleNextClick = () => {
navigate('/signup');
};
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

λ„€λΉ„κ²Œμ΄μ…˜ 둜직 였λ₯˜

"λ‹€μŒ" λ²„νŠΌ 클릭 μ‹œ /signup으둜 μ΄λ™ν•˜λŠ” 것은 μ˜λ„μ™€ λ‹€λ₯Ό 수 μžˆμŠ΅λ‹ˆλ‹€. μ΄λŠ” μ‚¬μš©μžλ₯Ό λ‹€μ‹œ 첫 번째 단계(SignupNickname)둜 되돌릴 κ°€λŠ₯성이 μžˆμŠ΅λ‹ˆλ‹€.

νšŒμ›κ°€μž… μ™„λ£Œ ν›„μ˜ λͺ©μ μ§€λ₯Ό λͺ…ν™•νžˆ ν•˜κ³  μ˜¬λ°”λ₯Έ 경둜둜 μˆ˜μ •ν•˜μ„Έμš”:

const handleNextClick = () => {
  // νšŒμ›κ°€μž… μ™„λ£Œ ν›„ 이동할 μ˜¬λ°”λ₯Έ 경둜둜 μˆ˜μ • ν•„μš”
  // 예: 메인 νŽ˜μ΄μ§€, λŒ€μ‹œλ³΄λ“œ, λ˜λŠ” μ™„λ£Œ νŽ˜μ΄μ§€
  navigate('/'); // λ˜λŠ” μ μ ˆν•œ μ™„λ£Œ νŽ˜μ΄μ§€ 경둜
};
πŸ€– Prompt for AI Agents
In src/pages/signup/SignupGenre.tsx around lines 13 to 15, the handleNextClick
function currently navigates to '/signup', which may incorrectly send users back
to the first signup step. Update the navigate call to redirect users to the
appropriate post-signup destination, such as the main page, dashboard, or a
signup completion page, for example by changing the path to '/' or another
suitable route.

@heeeeyong heeeeyong changed the title [feat] Routing & Css setting feat: Routing & Css setting Jun 24, 2025
@heeeeyong heeeeyong merged commit 3b1212b into develop Jun 24, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

✨ Feature κΈ°λŠ₯ 개발 🎨 Html&css λ§ˆν¬μ—… & μŠ€νƒ€μΌλ§

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant