feat(home): Linear형 앱 셸 레이아웃 전환 - #91
Conversation
전역 좌측 레일과 컨텍스트 패널을 도입해서 홈, 리스트, 상세 페이지의 탐색 경험을 통일했어요. 홈 피드를 검색과 정렬 중심 구조로 재구성하고 테마 토글과 검색 가시성도 함께 정리했어요.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 200df1e03f
ℹ️ 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".
| }); | ||
| }} | ||
| className="relative p-2 rounded-lg hover:bg-[var(--color-grey-100)] transition-colors focus:outline-none focus-visible:ring-2 focus-visible:ring-[var(--color-toss-blue)]" | ||
| className="relative inline-flex h-11 w-[88px] items-center rounded-full border border-[var(--color-grey-200)] bg-[var(--color-grey-50)] px-2 focus:outline-none focus-visible:ring-2 focus-visible:ring-[var(--color-toss-blue)]" |
There was a problem hiding this comment.
The repository rule in /workspace/eunu-log/AGENTS.md explicitly says to never use arbitrary Tailwind values, but this change introduces w-[88px] (and similar bracketed values elsewhere in the new shell UI). Hard-coded bracket values bypass shared tokens/utilities, which makes future design-token updates inconsistent and increases maintenance drift across components.
Useful? React with 👍 / 👎.
| type="button" | ||
| onClick={() => query.toggle()} | ||
| className="inline-flex h-11 w-full items-center gap-3 rounded-full border border-[var(--color-grey-200)] bg-[var(--color-grey-50)] px-4 text-sm text-[var(--color-grey-500)] transition-colors hover:border-[var(--color-grey-300)] hover:text-[var(--color-grey-900)]" |
There was a problem hiding this comment.
The new global search trigger no longer emits the click analytics event when users open the command palette (onClick only toggles KBar). Since this commit also removes Header usage across pages, the previous AnalyticsEvents.click instrumentation from Header is effectively gone, so search-button engagement metrics will drop to zero and distort experiment/product analytics.
Useful? React with 👍 / 👎.
1 participant
Summary
Testing