Skip to content

화이트 모드 디자인 수정 - #36

Merged
xeunnie merged 8 commits into
mainfrom
develop
Mar 28, 2026
Merged

화이트 모드 디자인 수정#36
xeunnie merged 8 commits into
mainfrom
develop

Conversation

@xeunnie

@xeunnie xeunnie commented Mar 28, 2026

Copy link
Copy Markdown
Member

No description provided.

@netlify

netlify Bot commented Mar 28, 2026

Copy link
Copy Markdown

Deploy Preview for onmeeteven ready!

Name Link
🔨 Latest commit 91d47f6
🔍 Latest deploy log https://app.netlify.com/projects/onmeeteven/deploys/69c75b9b4ec7190007f5ff44
😎 Deploy Preview https://deploy-preview-36--onmeeteven.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify

netlify Bot commented Mar 28, 2026

Copy link
Copy Markdown

Deploy Preview for roaring-trifle-75aa77 ready!

Name Link
🔨 Latest commit 91d47f6
🔍 Latest deploy log https://app.netlify.com/projects/roaring-trifle-75aa77/deploys/69c75b9b36e3b3000898ee30
😎 Deploy Preview https://deploy-preview-36--roaring-trifle-75aa77.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Mar 28, 2026

Copy link
Copy Markdown
Contributor

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Updated (UTC)
✅ Deployment successful!
View logs
onmeet-frontend 91d47f6 Mar 28 2026, 04:40 AM

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Code Review

This pull request introduces a comprehensive design token system in global.css, replacing various inline Tailwind styles with reusable classes like om-card and om-input across the dashboard and meeting components. It also standardizes date and time formatting to the Asia/Seoul timezone and updates the employee retrieval API endpoint. Feedback includes addressing redundant CSS variable definitions and shadow applications in the global stylesheet, using CSS variables for background colors instead of hardcoded hex values, and renaming a function to better reflect its updated API endpoint. Additionally, it is recommended to ensure all date formatting functions consistently handle timezones to avoid discrepancies for users in different regions.

Comment on lines 92 to 95
export function formatMeetingDate(date: Date): string {
// format은 로컬 시간 기준이므로, Date 객체가 이미 올바르면 OK
return format(date, "yyyy년 MMM dd일 (eee)", { locale: ko });
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

high

formatMeetingDate 함수에 대한 주석에서 format 함수가 로컬 시간 기준이라고 언급되어 있습니다. 이는 다른 시간대 사용자의 경우 날짜가 다르게 표시될 수 있는 문제를 야기할 수 있습니다. 이 파일의 다른 날짜/시간 포맷 함수들이 Asia/Seoul 시간대로 표준화되고 있는 점을 고려할 때, 이 함수 또한 시간대를 인식하도록 수정하여 모든 사용자에게 일관된 KST 날짜를 보여주는 것이 좋습니다.

Comment thread client/app/global.css Outdated
Comment on lines 94 to 131
.light {
--background: 270 30% 98%;
--foreground: 270 30% 15%;
--background: 270 20% 96%;
--foreground: 270 40% 12%;

--card: 0 0% 100%;
--card-foreground: 270 30% 15%;
--card-foreground: 270 40% 12%;

--popover: 0 0% 100%;
--popover-foreground: 270 30% 15%;
--popover-foreground: 270 40% 12%;

--primary: 270 84% 56%;
--primary-foreground: 0 0% 100%;

--secondary: 270 30% 92%;
--secondary-foreground: 270 84% 56%;
--secondary: 270 25% 90%;
--secondary-foreground: 270 84% 50%;

--muted: 270 15% 75%;
--muted-foreground: 270 20% 40%;
--muted: 270 15% 70%;
--muted-foreground: 270 25% 35%;

--accent: 270 84% 56%;
--accent-foreground: 0 0% 100%;

--destructive: 0 84% 60%;
--destructive: 0 84% 55%;
--destructive-foreground: 0 0% 100%;

--border: 270 30% 90%;
--input: 270 20% 96%;
--border: 270 30% 85%;
--input: 270 20% 92%;
--ring: 270 84% 56%;

--sidebar-background: 270 30% 98%;
--sidebar-foreground: 270 30% 15%;
--sidebar-background: 0 0% 100%;
--sidebar-foreground: 270 40% 12%;
--sidebar-primary: 270 84% 56%;
--sidebar-primary-foreground: 0 0% 100%;
--sidebar-accent: 270 30% 94%;
--sidebar-accent-foreground: 270 84% 50%;
--sidebar-border: 270 30% 90%;
--sidebar-accent: 270 30% 92%;
--sidebar-accent-foreground: 270 84% 45%;
--sidebar-border: 270 25% 88%;
--sidebar-ring: 270 84% 56%;
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

.light 선택자에 정의된 CSS 변수들이 :root에 정의된 변수들과 동일합니다. 이는 코드 중복으로, 유지보수성을 떨어뜨릴 수 있습니다. :root가 기본(라이트) 테마를 정의하므로, .light 블록 전체를 제거하여 중복을 피하는 것이 좋습니다.

Comment thread client/app/global.css Outdated
Comment on lines 143 to 149
body.dark {
background: linear-gradient(145deg, hsl(270, 30%, 6%) 0%, hsl(280, 20%, 4%) 40%, hsl(300, 15%, 8%) 100%);
background-attachment: fixed;
background: #0a0612;
}

body.light {
background: linear-gradient(145deg, hsl(270, 40%, 97%) 0%, hsl(0, 0%, 100%) 40%, hsl(330, 30%, 97%) 100%);
background-attachment: fixed;
background: #f5f3f7;
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

body.darkbody.light의 배경색으로 하드코딩된 hex 값이 사용되고 있습니다. 일관성을 유지하고 향후 테마 업데이트를 용이하게 하려면 --background CSS 변수를 사용하는 것이 좋습니다. 예를 들어, background: hsl(var(--background));와 같이 사용할 수 있습니다. 만약 현재 하드코딩된 색상이 의도된 것이라면, 해당 색상 값을 CSS 변수 자체에 정의하는 것을 고려해 보세요.

Suggested change
body.dark {
background: linear-gradient(145deg, hsl(270, 30%, 6%) 0%, hsl(280, 20%, 4%) 40%, hsl(300, 15%, 8%) 100%);
background-attachment: fixed;
background: #0a0612;
}
body.light {
background: linear-gradient(145deg, hsl(270, 40%, 97%) 0%, hsl(0, 0%, 100%) 40%, hsl(330, 30%, 97%) 100%);
background-attachment: fixed;
background: #f5f3f7;
}
body.dark {
background: hsl(var(--background));
}
body.light {
background: hsl(var(--background));
}

Comment thread client/app/global.css Outdated
Comment on lines +197 to +198
@apply bg-white border border-purple-200/60 hover:border-purple-300
shadow-md hover:shadow-lg;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

.light .om-card 클래스에서 @apply를 통해 shadow-mdhover:shadow-lg를 적용하고 있지만, 바로 다음에 box-shadow 속성으로 덮어쓰고 있습니다. 이는 코드를 혼란스럽게 만들 수 있으며 중복입니다. @apply에서 shadow-mdhover:shadow-lg를 제거하여 코드를 명확하게 하는 것이 좋습니다.

  @apply bg-white border border-purple-200/60 hover:border-purple-300;

Comment thread client/app/global.css Outdated
Comment on lines +316 to +317
@apply bg-white border border-purple-200/60
shadow-md;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

.om-card와 유사하게, .light .om-panel 클래스에서도 @apply를 통해 shadow-md를 적용한 후 별도의 box-shadow 속성으로 덮어쓰고 있습니다. 혼란을 피하기 위해 @apply에서 shadow-md를 제거하는 것이 좋습니다.

  @apply bg-white border border-purple-200/60;

Comment thread client/features/auth/api/manager.ts Outdated
Comment on lines 16 to 20
export function getAllEmployees(
pageable: Pageable,
): Promise<PageResponse<UserResponseDto>> {
return authFetch(`/v1/manager/employees${pageQs(pageable)}`);
return authFetch(`/v1/members/invitable${pageQs(pageable)}`);
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

getAllEmployees 함수가 이제 /v1/members/invitable 엔드포인트를 호출합니다. 함수 이름이 API가 제공하는 기능("초대 가능한 멤버 조회")과 일치하지 않아 오해를 살 수 있습니다. getInvitableMembers와 같이 API의 역할을 더 잘 나타내는 이름으로 변경하는 것을 고려해 보세요.

@xeunnie
xeunnie merged commit a97ed42 into main Mar 28, 2026
13 checks passed
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