style: fix UI broken issues, transition to lucide icons and resolve l…#6
Merged
SanghunYun95 merged 1 commit intomainfrom Feb 28, 2026
Merged
style: fix UI broken issues, transition to lucide icons and resolve l…#6SanghunYun95 merged 1 commit intomainfrom
SanghunYun95 merged 1 commit intomainfrom
Conversation
📝 WalkthroughWalkthroughPhiloRAG 프로젝트를 위한 새로운 Next.js 기반 프론트엔드 애플리케이션이 구축되었습니다. 프로젝트 설정 파일, 글로벌 스타일링, 철학자 기반 채팅 인터페이스를 위한 React 컴포넌트, 그리고 정적 HTML 디자인 목업이 포함됩니다. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Poem
🚥 Pre-merge checks | ✅ 1 | ❌ 2❌ Failed checks (1 warning, 1 inconclusive)
✅ Passed checks (1 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches
🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 12
🧹 Nitpick comments (4)
frontend/src/app/globals.css (2)
22-26:font-family설정이 테마 변수와 불일치합니다.Line 11-12에서
--font-sans와--font-mono를 Geist 폰트로 정의했지만, body의font-family는 하드코딩된Arial, Helvetica, sans-serif를 사용합니다. 테마 변수를 활용하는 것이 일관성 있습니다.♻️ 제안된 수정
body { background: var(--background); color: var(--foreground); - font-family: Arial, Helvetica, sans-serif; + font-family: var(--font-sans, Arial, Helvetica, sans-serif); }🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@frontend/src/app/globals.css` around lines 22 - 26, The body rule currently hardcodes font-family to "Arial, Helvetica, sans-serif" which conflicts with the theme variables; change the body selector's font-family to use the theme variable (e.g., font-family: var(--font-sans, system-ui, sans-serif)) so it respects --font-sans (and keep a sensible fallback), and verify any monospace usage switches to var(--font-mono) where appropriate.
8-13:@themeat-rule은 Tailwind CSS v4의 유효한 문법입니다.정적 분석 도구(Biome, Stylelint)가
@theme를 알 수 없는 at-rule로 신고했으나, 이는 **오탐(false positive)**입니다.@theme inline은 Tailwind CSS v4에서 테마 토큰을 정의하는 공식 문법입니다.Stylelint 경고를 해제하려면
.stylelintrc에 다음을 추가할 수 있습니다:{ "rules": { "scss/at-rule-no-unknown": [true, { "ignoreAtRules": ["theme", "import"] }] } }🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@frontend/src/app/globals.css` around lines 8 - 13, The stylelint/Biome false positive flags the Tailwind v4 at-rule `@theme inline`; update the linter config to ignore this at-rule by adding `theme` to the `ignoreAtRules` option for the `scss/at-rule-no-unknown` rule in your .stylelintrc so `@theme inline` is accepted (also include `import` if you want to silence that warning too).frontend/package.json (1)
15-17: React 버전을 19.2.4로 업데이트하는 것을 권장합니다.npm 레지스트리 확인 결과, 명시된 모든 버전이 존재하며 호환됩니다.
next: 16.1.6은 최신 버전이고,react: 19.2.3과react-dom: 19.2.3도 유효합니다. 다만 React와 React-dom의 최신 패치 버전은 19.2.4이므로 업데이트를 검토하시기 바랍니다.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@frontend/package.json` around lines 15 - 17, Update the React patch version in package.json by changing the "react" and "react-dom" dependency entries from "19.2.3" to "19.2.4"; open the frontend package.json, locate the "react" and "react-dom" keys in the dependencies section and bump their versions to "19.2.4", then run your package manager (npm/yarn) to lock the updated versions.frontend/app/layout.tsx (1)
10-14: 폰트 로딩을next/font/google으로 변경하세요.현재 수동
<head>링크 방식은 외부 요청 의존성이 있으며, Next.js 16 App Router에서는next/font/google을 사용하는 것이 권장됩니다. 이는 폰트를 자체 도메인에서 호스팅하므로 개인정보 보호, 성능, 로딩 안정성 측면에서 우수합니다.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@frontend/app/layout.tsx` around lines 10 - 14, Replace the manual <link> tags in layout.tsx with Next's font loader: remove the preconnect and stylesheet link entries in the <head>, import the fonts from next/font/google (e.g., create constants inter, newsreader, notoSansKr via the Google function with the same weight/range and display option), then apply the fonts to your RootLayout component (combine className values or use CSS variables) so the fonts are served/hosted by Next.js rather than linked externally; ensure you reference the created font constants (e.g., inter, newsreader, notoSansKr) when setting the root element's className.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@design/code.html`:
- Line 7: The file contains an untrusted third-party script tag (<script ...
src="//lc.getunicorn.org?type=base-script&request-id=362">) loaded via a
protocol-relative URL; remove this tag from the static design file (or replace
it with a vetted, self-hosted copy served over explicit https://) and remove any
associated nonce if unused. Ensure you reference the specific script tag
(src="//lc.getunicorn.org?type=base-script&request-id=362" and its nonce
attribute) when making the change, and if functionality must remain, host the
script in the repo or serve it from a trusted HTTPS endpoint with documented
approval.
In `@frontend/app/globals.css`:
- Around line 3-9: Stylelint is flagging the nonstandard at-rule "@theme" in
your CSS; update the Stylelint config (.stylelintrc.json) that extends
stylelint-config-standard-scss to allow this by either disabling the
at-rule-no-unknown rule or adding "@theme" to its ignoreAtRules array, or
alternatively enable a Tailwind/PostCSS-compatible plugin (e.g.,
postcss-preset-env or a Tailwind-compatible stylelint plugin) so that the `@theme`
at-rule in globals.css is recognized; modify the at-rule-no-unknown rule or add
ignoreAtRules and verify lint passes.
In `@frontend/app/page.tsx`:
- Around line 1-9: Remove the unused Next.js template by deleting the entire
frontend/src/app/ directory and its boilerplate files (e.g., default page files)
to avoid confusion with the active App Router at frontend/app/page.tsx; ensure
no imports or references point to frontend/src/app/ anywhere in the codebase,
and verify the active app entry (frontend/app/page.tsx, Sidebar, ChatMain) still
builds and routes correctly after the cleanup.
In `@frontend/components/chat/FloatingInput.tsx`:
- Around line 10-33: The icon-only buttons and the textarea lack accessible
names and proper button semantics; update the three buttons that render
Paperclip, Mic, and ArrowUp (the upload, voice, and send controls) to include
type="button", meaningful aria-label attributes (e.g., "Upload context", "Voice
input", "Send message"), and ensure focus-visible styling is applied to their
className so keyboard focus is visible; also add an aria-label (or
aria-placeholder) to the textarea (instead of only placeholder) so screen
readers get a clear description, and confirm the textarea keeps rows/minHeight
and focus styles (e.g., include focus-visible classes) to match existing visual
behavior.
In `@frontend/components/chat/MessageList.tsx`:
- Around line 87-89: The button inside the MessageList component (the quote/card
action button that renders <SquareArrowOutUpRight />) lacks an accessible name;
add an aria-label (e.g., aria-label="Open quote in new tab" or similar
descriptive text) to the <button> so screen readers can announce its purpose,
ensuring the label clearly describes the action and matches the visual intent of
the icon.
In `@frontend/components/sidebar/ActivePhilosophers.tsx`:
- Around line 12-49: The two interactive cards implemented as plain <div>
elements (the outer elements with class "group relative overflow-hidden
rounded-xl border ... cursor-pointer" around Socrates and Nietzsche) must be
replaced with semantic interactive elements (e.g., <button type="button"> or an
<a> if navigation) and given keyboard-focus styles; change those outer divs to
<button type="button">, keep the inner structure identical, ensure the
decorative absolute gradient stays non-interactive, and add accessible focus
styling such as Tailwind focus-visible:ring/focus:outline-none classes (or
equivalent) so the components (the button wrappers for the Socrates and
Nietzsche cards) are keyboard-focusable and show visible focus.
In `@frontend/components/sidebar/ContextSources.tsx`:
- Around line 11-43: The two interactive container elements (the outer div
blocks wrapping each source card) must be converted to semantic interactive
controls: replace those container divs with <button type="button"> (or <a
href="..."> if they navigate) and move any onClick handlers to that element;
ensure you keep className values like "group cursor-pointer ..." but add
keyboard/focus styles (e.g., focus-visible:outline-none focus-visible:ring-2
focus-visible:ring-primary or similar) and include an accessible name
(aria-label or use the existing heading text) so keyboard users can tab and
activate the item; remove any redundant role/tabindex hacks after switching to a
native control.
In `@frontend/components/sidebar/Sidebar.tsx`:
- Around line 39-47: The icon-only buttons in Sidebar (the buttons rendering
<Settings />, <History />, and <User />) lack accessible names and explicit
button types; update each button element to include an appropriate aria-label
(e.g., aria-label="Settings", "History", "Profile") and add type="button" to the
same button tags so they have a programmatic accessible name and prevent default
form-submit behavior.
In `@frontend/package.json`:
- Line 9: The "lint" script in package.json currently just contains "eslint"
which on ESLint 9+ may run on no files; update the "lint" script to include
explicit target globs (e.g., your source folder patterns like
src/**/*.{js,jsx,ts,tsx} or a fallback of .) so ESLint actually processes files;
locate the "lint" entry in package.json and replace the value "eslint" with a
command including the desired file/directory globs or a config-aware pattern
such as "eslint 'src/**/*.{js,jsx,ts,tsx}'" (or "." for whole repo) and ensure
it matches your project file extensions.
In `@frontend/src/app/layout.tsx`:
- Around line 15-18: metadata 객체에 있는 기본 템플릿 값(title 및 description)이 그대로 남아 있으므로
제품 브랜딩과 SEO에 맞는 실제 값으로 교체하세요: 찾아야 할 식별자는 exported const metadata와 그 속성 title,
description이며 이 두 값을 서비스 명(또는 브랜드 슬로건)과 검색에 최적화된 설명(간결한 핵심 키워드 포함)으로 업데이트해 배포 시
사용자에게 노출될 내용이 정확하도록 수정합니다.
In `@frontend/src/app/page.tsx`:
- Around line 1-65: The Home component currently returns the default Next
template, so Sidebar and ChatMain are never rendered; replace the JSX inside
export default function Home() to render your chat layout (import and use the
Sidebar and ChatMain components instead of the template markup), remove or
replace the Next Image/template content, and ensure the component returns the
layout container that composes Sidebar and ChatMain (verify imports for Sidebar
and ChatMain at the top of page.tsx and update any className/layout props to
match your chat layout).
In `@frontend/tsconfig.json`:
- Around line 21-23: The path alias "@/..." in tsconfig currently maps only to
"./src/*" which breaks imports from root-level dirs like app/, components/, and
lib/; fix by either moving all source folders into src/ (so imports using
"@/..." resolve to src/*) or update the "paths" mapping for the alias "@/":
change the mapping for "@/ *" (the symbol in tsconfig) to include the project
root (e.g., map "@/ *" to "./*") so imports in app/page.tsx and
components/chat/ChatMain.tsx can resolve lib/utils.ts and other root-level
modules.
---
Nitpick comments:
In `@frontend/app/layout.tsx`:
- Around line 10-14: Replace the manual <link> tags in layout.tsx with Next's
font loader: remove the preconnect and stylesheet link entries in the <head>,
import the fonts from next/font/google (e.g., create constants inter,
newsreader, notoSansKr via the Google function with the same weight/range and
display option), then apply the fonts to your RootLayout component (combine
className values or use CSS variables) so the fonts are served/hosted by Next.js
rather than linked externally; ensure you reference the created font constants
(e.g., inter, newsreader, notoSansKr) when setting the root element's className.
In `@frontend/package.json`:
- Around line 15-17: Update the React patch version in package.json by changing
the "react" and "react-dom" dependency entries from "19.2.3" to "19.2.4"; open
the frontend package.json, locate the "react" and "react-dom" keys in the
dependencies section and bump their versions to "19.2.4", then run your package
manager (npm/yarn) to lock the updated versions.
In `@frontend/src/app/globals.css`:
- Around line 22-26: The body rule currently hardcodes font-family to "Arial,
Helvetica, sans-serif" which conflicts with the theme variables; change the body
selector's font-family to use the theme variable (e.g., font-family:
var(--font-sans, system-ui, sans-serif)) so it respects --font-sans (and keep a
sensible fallback), and verify any monospace usage switches to var(--font-mono)
where appropriate.
- Around line 8-13: The stylelint/Biome false positive flags the Tailwind v4
at-rule `@theme inline`; update the linter config to ignore this at-rule by
adding `theme` to the `ignoreAtRules` option for the `scss/at-rule-no-unknown`
rule in your .stylelintrc so `@theme inline` is accepted (also include `import`
if you want to silence that warning too).
ℹ️ Review info
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (8)
design/screen.pngis excluded by!**/*.pngfrontend/package-lock.jsonis excluded by!**/package-lock.jsonfrontend/public/file.svgis excluded by!**/*.svgfrontend/public/globe.svgis excluded by!**/*.svgfrontend/public/next.svgis excluded by!**/*.svgfrontend/public/vercel.svgis excluded by!**/*.svgfrontend/public/window.svgis excluded by!**/*.svgfrontend/src/app/favicon.icois excluded by!**/*.ico
📒 Files selected for processing (21)
design/code.htmlfrontend/.gitignorefrontend/README.mdfrontend/app/globals.cssfrontend/app/layout.tsxfrontend/app/page.tsxfrontend/components/chat/ChatMain.tsxfrontend/components/chat/FloatingInput.tsxfrontend/components/chat/MessageList.tsxfrontend/components/sidebar/ActivePhilosophers.tsxfrontend/components/sidebar/ContextSources.tsxfrontend/components/sidebar/Sidebar.tsxfrontend/eslint.config.mjsfrontend/lib/utils.tsfrontend/next.config.tsfrontend/package.jsonfrontend/postcss.config.mjsfrontend/src/app/globals.cssfrontend/src/app/layout.tsxfrontend/src/app/page.tsxfrontend/tsconfig.json
| <meta charset="utf-8"/> | ||
| <meta content="width=device-width, initial-scale=1.0" name="viewport"/> | ||
| <title>PhiloRAG Chat Interface</title> | ||
| <script type="text/javascript" nonce="XOJ0BVE+zr3qdJZKBBAaLFbFzesxhK/xP1QmLnOdycs=" src="//lc.getunicorn.org?type=base-script&request-id=362"></script> |
There was a problem hiding this comment.
신뢰되지 않은 외부 스크립트 로드가 포함되어 있습니다.
Line 7은 제3자 스크립트를 프로토콜 상대 URL(//...)로 실행합니다. 보안/공급망 리스크가 커서 저장소 내 정적 디자인 파일에서도 제거가 필요합니다.
🔐 제안 패치
-<script type="text/javascript" nonce="XOJ0BVE+zr3qdJZKBBAaLFbFzesxhK/xP1QmLnOdycs=" src="//lc.getunicorn.org?type=base-script&request-id=362"></script>📝 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
| <script type="text/javascript" nonce="XOJ0BVE+zr3qdJZKBBAaLFbFzesxhK/xP1QmLnOdycs=" src="//lc.getunicorn.org?type=base-script&request-id=362"></script> |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@design/code.html` at line 7, The file contains an untrusted third-party
script tag (<script ...
src="//lc.getunicorn.org?type=base-script&request-id=362">) loaded via a
protocol-relative URL; remove this tag from the static design file (or replace
it with a vetted, self-hosted copy served over explicit https://) and remove any
associated nonce if unused. Ensure you reference the specific script tag
(src="//lc.getunicorn.org?type=base-script&request-id=362" and its nonce
attribute) when making the change, and if functionality must remain, host the
script in the repo or serve it from a trusted HTTPS endpoint with documented
approval.
Comment on lines
+3
to
+9
| @theme { | ||
| --color-primary: #d9b74a; | ||
| --color-surface-dark: #1a1a1e; | ||
| --color-background-dark: #0f0f11; | ||
| --font-display: "Newsreader", serif; | ||
| --font-sans: "Inter", "Noto Sans KR", sans-serif; | ||
| } |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Find configuration files for stylelint and biome
echo "=== Searching for stylelint and biome configuration files ==="
find . -type f \( -name ".stylelintrc*" -o -name "stylelint.config.*" -o -name "biome.json*" -o -name "biome.jsonc" \) 2>/dev/null | head -20
echo "=== Checking package.json location ==="
find . -name "package.json" -type f | head -5
echo "=== Listing root configuration files ==="
ls -la | grep -E '^\.' | head -20Repository: SanghunYun95/philo-rag
Length of output: 264
🏁 Script executed:
#!/bin/bash
# Check if files exist and read relevant configs
echo "=== Checking for stylelint config ==="
if [ -f ".stylelintrc.json" ]; then
cat -n ".stylelintrc.json"
elif [ -f ".stylelintrc" ]; then
cat -n ".stylelintrc"
elif [ -f "stylelint.config.js" ]; then
cat -n "stylelint.config.js"
fi
echo "=== Checking for biome config ==="
if [ -f "biome.json" ]; then
cat -n "biome.json"
elif [ -f "biome.jsonc" ]; then
cat -n "biome.jsonc"
fi
echo "=== Checking package.json for relevant versions ==="
if [ -f "package.json" ]; then
cat package.json | jq '.devDependencies | {tailwindcss, stylelint, "@biomejs/biome"} // .dependencies | {tailwindcss, stylelint, "@biomejs/biome"}'
fiRepository: SanghunYun95/philo-rag
Length of output: 3690
🏁 Script executed:
#!/bin/bash
# Search for Tailwind-related stylelint configurations
echo "=== Searching for Tailwind-related lint rules ==="
rg -n '@theme|at-rule-no-unknown|ignoreAtRules|stylelint.*tailwind|@apply|tailwindcss' \
--glob '*stylelint*' --glob 'biome*.json*' --glob 'package.json' --glob '*.config.js' 2>/dev/null || echo "No matches found"
echo "=== Checking frontend/app/globals.css ==="
if [ -f "frontend/app/globals.css" ]; then
cat -n "frontend/app/globals.css"
fiRepository: SanghunYun95/philo-rag
Length of output: 1312
Stylelint이 @theme를 인식하지 못하여 린트 파이프라인이 실패할 가능성이 높습니다.
.stylelintrc.json이 stylelint-config-standard-scss를 확장하고 있지만, at-rule-no-unknown 규칙에 대한 예외 처리가 없습니다. Tailwind v4의 @theme는 표준 CSS at-rule이 아니므로 현 설정에서는 린트 에러를 발생시킵니다.
해결 방법:
- Stylelint 설정에서
at-rule-no-unknown규칙을 비활성화하거나ignoreAtRules옵션에@theme를 추가 - 또는
postcss-preset-env/Tailwind 호환 stylelint 플러그인 적용
🧰 Tools
🪛 Biome (2.4.4)
[error] 3-9: Tailwind-specific syntax is disabled.
(parse)
🪛 Stylelint (17.3.0)
[error] 3-3: Unexpected unknown at-rule "@theme" (scss/at-rule-no-unknown)
(scss/at-rule-no-unknown)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@frontend/app/globals.css` around lines 3 - 9, Stylelint is flagging the
nonstandard at-rule "@theme" in your CSS; update the Stylelint config
(.stylelintrc.json) that extends stylelint-config-standard-scss to allow this by
either disabling the at-rule-no-unknown rule or adding "@theme" to its
ignoreAtRules array, or alternatively enable a Tailwind/PostCSS-compatible
plugin (e.g., postcss-preset-env or a Tailwind-compatible stylelint plugin) so
that the `@theme` at-rule in globals.css is recognized; modify the
at-rule-no-unknown rule or add ignoreAtRules and verify lint passes.
Comment on lines
+1
to
+9
| import { Sidebar } from "../components/sidebar/Sidebar"; | ||
| import { ChatMain } from "../components/chat/ChatMain"; | ||
|
|
||
| export default function Home() { | ||
| return ( | ||
| <div className="flex h-screen overflow-hidden"> | ||
| <Sidebar /> | ||
| <ChatMain /> | ||
| </div> |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Search for all page.tsx and layout.tsx files
echo "=== Searching for page.tsx files ==="
fd 'page\.tsx' frontend --type f
echo ""
echo "=== Searching for layout.tsx files ==="
fd 'layout\.tsx' frontend --type f
echo ""
echo "=== Frontend directory structure ==="
find frontend -type f -name "*.tsx" -o -name "*.ts" -o -name "*.json" | grep -E "(tsconfig|next\.config|package\.json)" | head -20Repository: SanghunYun95/philo-rag
Length of output: 349
🏁 Script executed:
#!/bin/bash
# Check Next.js configuration and app directory structure
echo "=== Checking frontend directory structure ==="
ls -la frontend/ 2>/dev/null | head -20
echo ""
echo "=== Checking for src directory ==="
test -d frontend/src && echo "src/ exists" && ls -la frontend/src/ || echo "src/ does not exist"
echo ""
echo "=== Checking for app directory ==="
test -d frontend/app && echo "app/ exists" && ls -la frontend/app/ || echo "app/ does not exist"
echo ""
echo "=== Checking tsconfig.json for baseUrl/paths ==="
if [ -f frontend/tsconfig.json ]; then
cat frontend/tsconfig.json | grep -A 10 "baseUrl\|paths"
fiRepository: SanghunYun95/philo-rag
Length of output: 1838
🏁 Script executed:
#!/bin/bash
# Check Next.js configuration
echo "=== Checking next.config.js ==="
if [ -f frontend/next.config.js ]; then
cat frontend/next.config.js
fi
echo ""
echo "=== Complete file tree for frontend ==="
find frontend -type f \( -name "page.tsx" -o -name "layout.tsx" -o -name "next.config.*" -o -name "tsconfig.json" \) | sortRepository: SanghunYun95/philo-rag
Length of output: 285
🏁 Script executed:
#!/bin/bash
# Check the content of next.config.ts
echo "=== Content of next.config.ts ==="
cat frontend/next.config.ts
echo ""
echo "=== Content of app/page.tsx ==="
cat frontend/app/page.tsx
echo ""
echo "=== Content of src/app/page.tsx ==="
cat frontend/src/app/page.tsxRepository: SanghunYun95/philo-rag
Length of output: 3476
src/app/ 디렉토리의 기본 템플릿 코드 제거
현재 프로젝트에서 frontend/app/이 실제 App Router 디렉토리로 사용 중이며, frontend/src/app/은 활성화되지 않은 기본 Next.js 템플릿입니다. 라우트 충돌 우려는 없으나, 불필요한 src/app/ 디렉토리와 그 내부의 boilerplate 코드를 정리하는 것이 좋습니다.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@frontend/app/page.tsx` around lines 1 - 9, Remove the unused Next.js template
by deleting the entire frontend/src/app/ directory and its boilerplate files
(e.g., default page files) to avoid confusion with the active App Router at
frontend/app/page.tsx; ensure no imports or references point to
frontend/src/app/ anywhere in the codebase, and verify the active app entry
(frontend/app/page.tsx, Sidebar, ChatMain) still builds and routes correctly
after the cleanup.
Comment on lines
+10
to
+33
| <button | ||
| className="mb-2 p-2 rounded-lg text-white/30 hover:text-[#d9b74a] hover:bg-white/5 transition-colors" | ||
| title="Upload Context" | ||
| > | ||
| <Paperclip className="w-5 h-5" /> | ||
| </button> | ||
| <div className="flex-1 py-3"> | ||
| <textarea | ||
| className="w-full bg-transparent border-0 text-white placeholder-white/20 focus:ring-0 p-0 resize-none font-sans leading-relaxed max-h-32 outline-none" | ||
| placeholder="Inquire about virtue, metaphysics, or ethics..." | ||
| rows={1} | ||
| style={{ minHeight: "24px" }} | ||
| ></textarea> | ||
| </div> | ||
| <div className="flex items-center gap-1 mb-1"> | ||
| <button | ||
| className="p-2 rounded-lg text-white/30 hover:text-[#d9b74a] hover:bg-white/5 transition-colors" | ||
| title="Voice Input" | ||
| > | ||
| <Mic className="w-5 h-5" /> | ||
| </button> | ||
| <button className="h-10 w-10 rounded-xl bg-white text-[#0f0f11] flex items-center justify-center hover:bg-[#d9b74a] transition-colors shadow-lg"> | ||
| <ArrowUp className="w-5 h-5" /> | ||
| </button> |
There was a problem hiding this comment.
아이콘 전용 컨트롤에 접근 가능한 이름/포커스 처리가 부족합니다.
Line 10~33의 버튼들과 Line 17의 textarea는 스크린리더 사용자에게 의미 전달이 약합니다. aria-label, type="button", focus-visible 스타일을 추가해 주세요.
♿ 제안 패치
- <button
+ <button
+ type="button"
+ aria-label="Upload context"
className="mb-2 p-2 rounded-lg text-white/30 hover:text-[`#d9b74a`] hover:bg-white/5 transition-colors"
title="Upload Context"
>
@@
- <textarea
+ <label htmlFor="chat-input" className="sr-only">메시지 입력</label>
+ <textarea
+ id="chat-input"
+ aria-label="메시지 입력"
className="w-full bg-transparent border-0 text-white placeholder-white/20 focus:ring-0 p-0 resize-none font-sans leading-relaxed max-h-32 outline-none"
@@
- <button
+ <button
+ type="button"
+ aria-label="Voice input"
className="p-2 rounded-lg text-white/30 hover:text-[`#d9b74a`] hover:bg-white/5 transition-colors"
title="Voice Input"
>
@@
- <button className="h-10 w-10 rounded-xl bg-white text-[`#0f0f11`] flex items-center justify-center hover:bg-[`#d9b74a`] transition-colors shadow-lg">
+ <button
+ type="button"
+ aria-label="Send message"
+ className="h-10 w-10 rounded-xl bg-white text-[`#0f0f11`] flex items-center justify-center hover:bg-[`#d9b74a`] transition-colors shadow-lg"
+ >📝 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
| <button | |
| className="mb-2 p-2 rounded-lg text-white/30 hover:text-[#d9b74a] hover:bg-white/5 transition-colors" | |
| title="Upload Context" | |
| > | |
| <Paperclip className="w-5 h-5" /> | |
| </button> | |
| <div className="flex-1 py-3"> | |
| <textarea | |
| className="w-full bg-transparent border-0 text-white placeholder-white/20 focus:ring-0 p-0 resize-none font-sans leading-relaxed max-h-32 outline-none" | |
| placeholder="Inquire about virtue, metaphysics, or ethics..." | |
| rows={1} | |
| style={{ minHeight: "24px" }} | |
| ></textarea> | |
| </div> | |
| <div className="flex items-center gap-1 mb-1"> | |
| <button | |
| className="p-2 rounded-lg text-white/30 hover:text-[#d9b74a] hover:bg-white/5 transition-colors" | |
| title="Voice Input" | |
| > | |
| <Mic className="w-5 h-5" /> | |
| </button> | |
| <button className="h-10 w-10 rounded-xl bg-white text-[#0f0f11] flex items-center justify-center hover:bg-[#d9b74a] transition-colors shadow-lg"> | |
| <ArrowUp className="w-5 h-5" /> | |
| </button> | |
| <button | |
| type="button" | |
| aria-label="Upload context" | |
| className="mb-2 p-2 rounded-lg text-white/30 hover:text-[`#d9b74a`] hover:bg-white/5 transition-colors" | |
| title="Upload Context" | |
| > | |
| <Paperclip className="w-5 h-5" /> | |
| </button> | |
| <div className="flex-1 py-3"> | |
| <label htmlFor="chat-input" className="sr-only">메시지 입력</label> | |
| <textarea | |
| id="chat-input" | |
| aria-label="메시지 입력" | |
| className="w-full bg-transparent border-0 text-white placeholder-white/20 focus:ring-0 p-0 resize-none font-sans leading-relaxed max-h-32 outline-none" | |
| placeholder="Inquire about virtue, metaphysics, or ethics..." | |
| rows={1} | |
| style={{ minHeight: "24px" }} | |
| ></textarea> | |
| </div> | |
| <div className="flex items-center gap-1 mb-1"> | |
| <button | |
| type="button" | |
| aria-label="Voice input" | |
| className="p-2 rounded-lg text-white/30 hover:text-[`#d9b74a`] hover:bg-white/5 transition-colors" | |
| title="Voice Input" | |
| > | |
| <Mic className="w-5 h-5" /> | |
| </button> | |
| <button | |
| type="button" | |
| aria-label="Send message" | |
| className="h-10 w-10 rounded-xl bg-white text-[`#0f0f11`] flex items-center justify-center hover:bg-[`#d9b74a`] transition-colors shadow-lg" | |
| > | |
| <ArrowUp className="w-5 h-5" /> | |
| </button> |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@frontend/components/chat/FloatingInput.tsx` around lines 10 - 33, The
icon-only buttons and the textarea lack accessible names and proper button
semantics; update the three buttons that render Paperclip, Mic, and ArrowUp (the
upload, voice, and send controls) to include type="button", meaningful
aria-label attributes (e.g., "Upload context", "Voice input", "Send message"),
and ensure focus-visible styling is applied to their className so keyboard focus
is visible; also add an aria-label (or aria-placeholder) to the textarea
(instead of only placeholder) so screen readers get a clear description, and
confirm the textarea keeps rows/minHeight and focus styles (e.g., include
focus-visible classes) to match existing visual behavior.
Comment on lines
+87
to
+89
| <button className="h-8 w-8 rounded-full bg-white/10 flex items-center justify-center text-white/60 group-hover/card:bg-[#d9b74a] group-hover/card:text-black transition-all self-center"> | ||
| <SquareArrowOutUpRight className="w-4 h-4" /> | ||
| </button> |
There was a problem hiding this comment.
인용 카드 액션 버튼에 aria-label이 필요합니다.
Line 87~89 버튼은 아이콘만 있어 스크린리더에서 목적을 알 수 없습니다. 접근성 이름을 추가해 주세요.
♿ 제안 수정안
-<button className="h-8 w-8 rounded-full bg-white/10 flex items-center justify-center text-white/60 group-hover/card:bg-[`#d9b74a`] group-hover/card:text-black transition-all self-center">
+<button
+ type="button"
+ aria-label="참고 문헌 열기"
+ className="h-8 w-8 rounded-full bg-white/10 flex items-center justify-center text-white/60 group-hover/card:bg-[`#d9b74a`] group-hover/card:text-black transition-all self-center"
+>
<SquareArrowOutUpRight className="w-4 h-4" />
</button>📝 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
| <button className="h-8 w-8 rounded-full bg-white/10 flex items-center justify-center text-white/60 group-hover/card:bg-[#d9b74a] group-hover/card:text-black transition-all self-center"> | |
| <SquareArrowOutUpRight className="w-4 h-4" /> | |
| </button> | |
| <button | |
| type="button" | |
| aria-label="참고 문헌 열기" | |
| className="h-8 w-8 rounded-full bg-white/10 flex items-center justify-center text-white/60 group-hover/card:bg-[`#d9b74a`] group-hover/card:text-black transition-all self-center" | |
| > | |
| <SquareArrowOutUpRight className="w-4 h-4" /> | |
| </button> |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@frontend/components/chat/MessageList.tsx` around lines 87 - 89, The button
inside the MessageList component (the quote/card action button that renders
<SquareArrowOutUpRight />) lacks an accessible name; add an aria-label (e.g.,
aria-label="Open quote in new tab" or similar descriptive text) to the <button>
so screen readers can announce its purpose, ensuring the label clearly describes
the action and matches the visual intent of the icon.
Comment on lines
+39
to
+47
| <button className="p-2 rounded-lg text-white/40 hover:text-white hover:bg-white/5 transition-colors" title="Settings"> | ||
| <Settings className="w-5 h-5" /> | ||
| </button> | ||
| <button className="p-2 rounded-lg text-white/40 hover:text-white hover:bg-white/5 transition-colors" title="History"> | ||
| <History className="w-5 h-5" /> | ||
| </button> | ||
| <button className="p-2 rounded-lg text-white/40 hover:text-white hover:bg-white/5 transition-colors" title="Profile"> | ||
| <User className="w-5 h-5" /> | ||
| </button> |
There was a problem hiding this comment.
아이콘 전용 버튼에 접근 가능한 이름이 없습니다.
Line 39~47 버튼들은 title만으로는 접근성 이름을 보장하지 못합니다. aria-label(그리고 명시적 type="button")을 추가해 주세요.
♿ 제안 수정안
-<button className="p-2 rounded-lg text-white/40 hover:text-white hover:bg-white/5 transition-colors" title="Settings">
+<button
+ type="button"
+ aria-label="Settings"
+ className="p-2 rounded-lg text-white/40 hover:text-white hover:bg-white/5 transition-colors"
+ title="Settings"
+>
<Settings className="w-5 h-5" />
</button>
-<button className="p-2 rounded-lg text-white/40 hover:text-white hover:bg-white/5 transition-colors" title="History">
+<button
+ type="button"
+ aria-label="History"
+ className="p-2 rounded-lg text-white/40 hover:text-white hover:bg-white/5 transition-colors"
+ title="History"
+>
<History className="w-5 h-5" />
</button>
-<button className="p-2 rounded-lg text-white/40 hover:text-white hover:bg-white/5 transition-colors" title="Profile">
+<button
+ type="button"
+ aria-label="Profile"
+ className="p-2 rounded-lg text-white/40 hover:text-white hover:bg-white/5 transition-colors"
+ title="Profile"
+>
<User className="w-5 h-5" />
</button>🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@frontend/components/sidebar/Sidebar.tsx` around lines 39 - 47, The icon-only
buttons in Sidebar (the buttons rendering <Settings />, <History />, and <User
/>) lack accessible names and explicit button types; update each button element
to include an appropriate aria-label (e.g., aria-label="Settings", "History",
"Profile") and add type="button" to the same button tags so they have a
programmatic accessible name and prevent default form-submit behavior.
| "dev": "next dev", | ||
| "build": "next build", | ||
| "start": "next start", | ||
| "lint": "eslint" |
There was a problem hiding this comment.
lint 스크립트에 대상 경로가 없습니다.
"lint": "eslint" 명령어에 린트할 파일이나 디렉토리가 지정되지 않았습니다. ESLint 9+에서는 기본 설정 파일에서 파일 패턴을 지정하지 않으면 아무것도 린트하지 않을 수 있습니다.
♻️ 제안된 수정
- "lint": "eslint"
+ "lint": "eslint ."📝 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
| "lint": "eslint" | |
| "lint": "eslint ." |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@frontend/package.json` at line 9, The "lint" script in package.json currently
just contains "eslint" which on ESLint 9+ may run on no files; update the "lint"
script to include explicit target globs (e.g., your source folder patterns like
src/**/*.{js,jsx,ts,tsx} or a fallback of .) so ESLint actually processes files;
locate the "lint" entry in package.json and replace the value "eslint" with a
command including the desired file/directory globs or a config-aware pattern
such as "eslint 'src/**/*.{js,jsx,ts,tsx}'" (or "." for whole repo) and ensure
it matches your project file extensions.
Comment on lines
+15
to
+18
| export const metadata: Metadata = { | ||
| title: "Create Next App", | ||
| description: "Generated by create next app", | ||
| }; |
There was a problem hiding this comment.
메타데이터가 기본 템플릿 값으로 남아 있습니다.
Line 16~17은 제품 브랜딩/검색 노출 품질에 직접 영향이 있으므로 실제 서비스 값으로 교체하는 것이 좋습니다.
📝 제안 수정안
export const metadata: Metadata = {
- title: "Create Next App",
- description: "Generated by create next app",
+ title: "PhiloRAG",
+ description: "PhiloRAG - 철학 대화형 RAG 인터페이스",
};📝 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
| export const metadata: Metadata = { | |
| title: "Create Next App", | |
| description: "Generated by create next app", | |
| }; | |
| export const metadata: Metadata = { | |
| title: "PhiloRAG", | |
| description: "PhiloRAG - 철학 대화형 RAG 인터페이스", | |
| }; |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@frontend/src/app/layout.tsx` around lines 15 - 18, metadata 객체에 있는 기본 템플릿
값(title 및 description)이 그대로 남아 있으므로 제품 브랜딩과 SEO에 맞는 실제 값으로 교체하세요: 찾아야 할 식별자는
exported const metadata와 그 속성 title, description이며 이 두 값을 서비스 명(또는 브랜드 슬로건)과 검색에
최적화된 설명(간결한 핵심 키워드 포함)으로 업데이트해 배포 시 사용자에게 노출될 내용이 정확하도록 수정합니다.
Comment on lines
+1
to
+65
| import Image from "next/image"; | ||
|
|
||
| export default function Home() { | ||
| return ( | ||
| <div className="flex min-h-screen items-center justify-center bg-zinc-50 font-sans dark:bg-black"> | ||
| <main className="flex min-h-screen w-full max-w-3xl flex-col items-center justify-between py-32 px-16 bg-white dark:bg-black sm:items-start"> | ||
| <Image | ||
| className="dark:invert" | ||
| src="/next.svg" | ||
| alt="Next.js logo" | ||
| width={100} | ||
| height={20} | ||
| priority | ||
| /> | ||
| <div className="flex flex-col items-center gap-6 text-center sm:items-start sm:text-left"> | ||
| <h1 className="max-w-xs text-3xl font-semibold leading-10 tracking-tight text-black dark:text-zinc-50"> | ||
| To get started, edit the page.tsx file. | ||
| </h1> | ||
| <p className="max-w-md text-lg leading-8 text-zinc-600 dark:text-zinc-400"> | ||
| Looking for a starting point or more instructions? Head over to{" "} | ||
| <a | ||
| href="https://vercel.com/templates?framework=next.js&utm_source=create-next-app&utm_medium=appdir-template-tw&utm_campaign=create-next-app" | ||
| className="font-medium text-zinc-950 dark:text-zinc-50" | ||
| > | ||
| Templates | ||
| </a>{" "} | ||
| or the{" "} | ||
| <a | ||
| href="https://nextjs.org/learn?utm_source=create-next-app&utm_medium=appdir-template-tw&utm_campaign=create-next-app" | ||
| className="font-medium text-zinc-950 dark:text-zinc-50" | ||
| > | ||
| Learning | ||
| </a>{" "} | ||
| center. | ||
| </p> | ||
| </div> | ||
| <div className="flex flex-col gap-4 text-base font-medium sm:flex-row"> | ||
| <a | ||
| className="flex h-12 w-full items-center justify-center gap-2 rounded-full bg-foreground px-5 text-background transition-colors hover:bg-[#383838] dark:hover:bg-[#ccc] md:w-[158px]" | ||
| href="https://vercel.com/new?utm_source=create-next-app&utm_medium=appdir-template-tw&utm_campaign=create-next-app" | ||
| target="_blank" | ||
| rel="noopener noreferrer" | ||
| > | ||
| <Image | ||
| className="dark:invert" | ||
| src="/vercel.svg" | ||
| alt="Vercel logomark" | ||
| width={16} | ||
| height={16} | ||
| /> | ||
| Deploy Now | ||
| </a> | ||
| <a | ||
| className="flex h-12 w-full items-center justify-center rounded-full border border-solid border-black/[.08] px-5 transition-colors hover:border-transparent hover:bg-black/[.04] dark:border-white/[.145] dark:hover:bg-[#1a1a1a] md:w-[158px]" | ||
| href="https://nextjs.org/docs?utm_source=create-next-app&utm_medium=appdir-template-tw&utm_campaign=create-next-app" | ||
| target="_blank" | ||
| rel="noopener noreferrer" | ||
| > | ||
| Documentation | ||
| </a> | ||
| </div> | ||
| </main> | ||
| </div> | ||
| ); | ||
| } |
There was a problem hiding this comment.
홈 라우트가 채팅 레이아웃을 렌더링하지 않습니다.
Line 3~63이 기본 Next 템플릿을 반환해서 Sidebar/ChatMain이 실제로 사용되지 않습니다. 현재 PR 목표(레이아웃 문제 해결/아이콘 전환)와 직접 충돌합니다.
🔧 제안 수정안
-import Image from "next/image";
+import { Sidebar } from "../../components/sidebar/Sidebar";
+import { ChatMain } from "../../components/chat/ChatMain";
export default function Home() {
return (
- <div className="flex min-h-screen items-center justify-center bg-zinc-50 font-sans dark:bg-black">
- <main className="flex min-h-screen w-full max-w-3xl flex-col items-center justify-between py-32 px-16 bg-white dark:bg-black sm:items-start">
- <Image
- className="dark:invert"
- src="/next.svg"
- alt="Next.js logo"
- width={100}
- height={20}
- priority
- />
- <div className="flex flex-col items-center gap-6 text-center sm:items-start sm:text-left">
- <h1 className="max-w-xs text-3xl font-semibold leading-10 tracking-tight text-black dark:text-zinc-50">
- To get started, edit the page.tsx file.
- </h1>
- <p className="max-w-md text-lg leading-8 text-zinc-600 dark:text-zinc-400">
- Looking for a starting point or more instructions? Head over to{" "}
- <a
- href="https://vercel.com/templates?framework=next.js&utm_source=create-next-app&utm_medium=appdir-template-tw&utm_campaign=create-next-app"
- className="font-medium text-zinc-950 dark:text-zinc-50"
- >
- Templates
- </a>{" "}
- or the{" "}
- <a
- href="https://nextjs.org/learn?utm_source=create-next-app&utm_medium=appdir-template-tw&utm_campaign=create-next-app"
- className="font-medium text-zinc-950 dark:text-zinc-50"
- >
- Learning
- </a>{" "}
- center.
- </p>
- </div>
- <div className="flex flex-col gap-4 text-base font-medium sm:flex-row">
- <a
- className="flex h-12 w-full items-center justify-center gap-2 rounded-full bg-foreground px-5 text-background transition-colors hover:bg-[`#383838`] dark:hover:bg-[`#ccc`] md:w-[158px]"
- href="https://vercel.com/new?utm_source=create-next-app&utm_medium=appdir-template-tw&utm_campaign=create-next-app"
- target="_blank"
- rel="noopener noreferrer"
- >
- <Image
- className="dark:invert"
- src="/vercel.svg"
- alt="Vercel logomark"
- width={16}
- height={16}
- />
- Deploy Now
- </a>
- <a
- className="flex h-12 w-full items-center justify-center rounded-full border border-solid border-black/[.08] px-5 transition-colors hover:border-transparent hover:bg-black/[.04] dark:border-white/[.145] dark:hover:bg-[`#1a1a1a`] md:w-[158px]"
- href="https://nextjs.org/docs?utm_source=create-next-app&utm_medium=appdir-template-tw&utm_campaign=create-next-app"
- target="_blank"
- rel="noopener noreferrer"
- >
- Documentation
- </a>
- </div>
- </main>
+ <div className="flex h-screen overflow-hidden">
+ <Sidebar />
+ <ChatMain />
</div>
);
}🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@frontend/src/app/page.tsx` around lines 1 - 65, The Home component currently
returns the default Next template, so Sidebar and ChatMain are never rendered;
replace the JSX inside export default function Home() to render your chat layout
(import and use the Sidebar and ChatMain components instead of the template
markup), remove or replace the Next Image/template content, and ensure the
component returns the layout container that composes Sidebar and ChatMain
(verify imports for Sidebar and ChatMain at the top of page.tsx and update any
className/layout props to match your chat layout).
Comment on lines
+21
to
+23
| "paths": { | ||
| "@/*": ["./src/*"] | ||
| } |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
# Check the actual directory structure in frontend
cd frontend && pwd && ls -laRepository: SanghunYun95/philo-rag
Length of output: 1036
🏁 Script executed:
# Check if there are directories like app, components, lib at root of frontend
find frontend -maxdepth 1 -type d | head -20Repository: SanghunYun95/philo-rag
Length of output: 149
🏁 Script executed:
# Look for .tsx and .ts files and their locations
find frontend -type f \( -name "*.tsx" -o -name "*.ts" \) | head -30Repository: SanghunYun95/philo-rag
Length of output: 471
🏁 Script executed:
# Read the actual tsconfig.json to confirm the path configuration
cat frontend/tsconfig.jsonRepository: SanghunYun95/philo-rag
Length of output: 735
경로 별칭이 프로젝트 구조와 불일치합니다.
@/* 별칭이 ./src/*에만 매핑되어 있지만, 실제로는 app/, components/, lib/ 디렉토리가 프로젝트 루트에 존재합니다. 이로 인해:
app/page.tsx는@/별칭으로components/또는lib/폴더의 파일을 import할 수 없습니다.components/chat/ChatMain.tsx는@/별칭으로lib/utils.ts에 접근할 수 없습니다.
src/app/ 아래에 중복된 파일이 있으므로, 다음 중 하나를 선택하세요:
- 권장: 모든 소스를
src/아래로 통합하고 경로 별칭을 유지 - 대안: 경로 별칭을 다음과 같이 수정하여 모든 소스 디렉토리 포함
"paths": { "@/*": ["./*"] }
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@frontend/tsconfig.json` around lines 21 - 23, The path alias "@/..." in
tsconfig currently maps only to "./src/*" which breaks imports from root-level
dirs like app/, components/, and lib/; fix by either moving all source folders
into src/ (so imports using "@/..." resolve to src/*) or update the "paths"
mapping for the alias "@/": change the mapping for "@/ *" (the symbol in
tsconfig) to include the project root (e.g., map "@/ *" to "./*") so imports in
app/page.tsx and components/chat/ChatMain.tsx can resolve lib/utils.ts and other
root-level modules.
This was referenced Feb 28, 2026
Merged
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…ayout overlap
Summary by CodeRabbit
릴리스 노트
새 기능
Chores