Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chore/storybook theme #97

Merged
merged 13 commits into from
Jan 12, 2025
Merged

Chore/storybook theme #97

merged 13 commits into from
Jan 12, 2025

Conversation

froggy1014
Copy link
Contributor

@froggy1014 froggy1014 commented Jan 12, 2025

Changes

Visuals

AS-IS TO-BE
image image

Checklist

  • Have you written the functional specifications?
  • Have you written the test code?

Additional Discussion Points

Summary by CodeRabbit

  • Storybook 구성

    • Storybook 인터페이스의 컴포넌트 카테고리 구조를 Components/[ComponentName]으로 재구성
    • 새로운 Storybook 테마 및 파비콘 추가
    • 문서 페이지에 소개 섹션 생성
  • 의존성 업데이트

    • Storybook 및 React 관련 개발 의존성 추가 및 업데이트
    • Storybook 패키지 버전을 ^8.4.7로 업그레이드
  • 문서화

    • 디자인 시스템 소개 페이지에 로고 및 메타데이터 추가

@froggy1014 froggy1014 added the documentation Improvements or additions to documentation label Jan 12, 2025
@froggy1014 froggy1014 self-assigned this Jan 12, 2025
Copy link

changeset-bot bot commented Jan 12, 2025

⚠️ No Changeset found

Latest commit: 9e8d882

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

coderabbitai bot commented Jan 12, 2025

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 eslint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

.storybook/main.ts

Oops! Something went wrong! :(

ESLint: 9.17.0

ESLint couldn't find an eslint.config.(js|mjs|cjs) file.

From ESLint v9.0.0, the default configuration file is now eslint.config.js.
If you are using a .eslintrc.* file, please follow the migration guide
to update your configuration file to the new format:

https://eslint.org/docs/latest/use/configure/migration-guide

If you still have problems after following the migration guide, please stop by
https://eslint.org/chat/help to chat with the team.

워크스루

이 풀 리퀘스트는 Storybook 구성을 개선하고 구성 요소의 카테고리화를 재구조화하는 데 중점을 둡니다. .storybook/main.ts.storybook/manager.ts에서 Storybook 설정을 업데이트하고, 다양한 구성 요소의 스토리 파일에서 제목을 'Components/[ComponentName]'으로 변경했습니다. 또한 파비콘 추가, 의존성 업데이트, 문서 소개 페이지 스타일링 등의 변경 사항이 포함되어 있습니다.

변경 사항

파일 변경 요약
.storybook/main.ts Storybook 구성에 MDX 파일 포함, 파비콘 추가
.storybook/manager.ts 커스텀 다크 테마 설정
*.stories.tsx 구성 요소 제목을 'Components/[ComponentName]'으로 변경
package.json Storybook 및 TypeScript 관련 의존성 업데이트
docs/introduction.mdx 메타데이터 및 로고 스타일링 추가

제안된 라벨

enhancement

제안된 리뷰어

  • bae-sh
  • heeji289
  • hy57in
  • kimdaeyeobbb
  • developerjhp
  • synuns
  • noahluftyang

시 (토끼의 노래)

🐰 스토리북 여행, 컴포넌트의 춤
카테고리 넓히고 스타일 다듬어
파비콘 반짝, 테마는 우아하게
코드의 세계를 더욱 빛나게 해
토끼의 마법, 디자인 시스템 노래! 🌈

Finishing Touches

  • 📝 Generate Docstrings (Beta)

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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. (Beta)
  • @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

codecov bot commented Jan 12, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

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: 2

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 3ded0e0 and 9e8d882.

⛔ Files ignored due to path filters (3)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
  • public/assets/favicon.ico is excluded by !**/*.ico
  • public/assets/sipe_brand_logo.png is excluded by !**/*.png
📒 Files selected for processing (20)
  • .storybook/main.ts (2 hunks)
  • .storybook/manager.ts (1 hunks)
  • .templates/component/src/Component.stories.tsx (1 hunks)
  • docs/introduction.mdx (1 hunks)
  • package.json (1 hunks)
  • packages/Input/src/Input.stories.tsx (1 hunks)
  • packages/avatar/src/Avatar.stories.tsx (3 hunks)
  • packages/badge/src/Badge.stories.tsx (1 hunks)
  • packages/button/src/Button.stories.tsx (1 hunks)
  • packages/card/src/Card.stories.tsx (1 hunks)
  • packages/divider/src/Divider.stories.tsx (1 hunks)
  • packages/flex/src/Flex.stories.tsx (1 hunks)
  • packages/icon/src/Icons.stories.tsx (4 hunks)
  • packages/radio-group/src/RadioGroup.stories.tsx (1 hunks)
  • packages/skeleton/src/Skeleton.stories.tsx (1 hunks)
  • packages/switch/src/Switch.stories.tsx (1 hunks)
  • packages/tokens/src/Tokens.stories.tsx (1 hunks)
  • packages/tooltip/src/Tooltip.stories.tsx (1 hunks)
  • packages/typography/src/Typography.stories.tsx (1 hunks)
  • pnpm-workspace.yaml (1 hunks)
✅ Files skipped from review due to trivial changes (16)
  • .storybook/manager.ts
  • packages/card/src/Card.stories.tsx
  • .templates/component/src/Component.stories.tsx
  • packages/switch/src/Switch.stories.tsx
  • packages/tokens/src/Tokens.stories.tsx
  • packages/divider/src/Divider.stories.tsx
  • packages/Input/src/Input.stories.tsx
  • packages/flex/src/Flex.stories.tsx
  • packages/badge/src/Badge.stories.tsx
  • packages/avatar/src/Avatar.stories.tsx
  • packages/skeleton/src/Skeleton.stories.tsx
  • docs/introduction.mdx
  • packages/icon/src/Icons.stories.tsx
  • packages/radio-group/src/RadioGroup.stories.tsx
  • packages/typography/src/Typography.stories.tsx
  • packages/tooltip/src/Tooltip.stories.tsx
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: chromatic
🔇 Additional comments (4)
.storybook/main.ts (2)

5-5: 문서화 기능이 확장되었습니다.

docs 디렉토리의 MDX 파일을 스토리북에 포함시켜 문서화 기능이 향상되었습니다.


18-20: 파비콘 경로를 확인해주세요.

파비콘 경로가 올바르게 설정되어 있는지 확인이 필요합니다.

✅ Verification successful

파비콘 경로가 정상적으로 설정되어 있습니다.

파비콘 파일이 public/assets/favicon.ico에 존재하며, Storybook 설정의 상대 경로(../public/assets/favicon.ico)가 올바르게 구성되어 있습니다.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# 파비콘 파일의 존재 여부 확인
test -f public/assets/favicon.ico && echo "파비콘 파일이 존재합니다" || echo "파비콘 파일이 없습니다"

Length of output: 72

packages/button/src/Button.stories.tsx (1)

5-5: 컴포넌트 구조가 개선되었습니다.

'Components' 네임스페이스 아래에 버튼 컴포넌트를 배치하여 스토리북의 구조가 더 체계적으로 개선되었습니다.

package.json (1)

16-16: 사용하지 않는 의존성을 확인해주세요.

@clack/prompts 패키지가 여전히 의존성에 포함되어 있지만, 실제로 사용되고 있는지 확인이 필요합니다.

✅ Verification successful

@clack/prompts 패키지는 컴포넌트 생성 CLI에서 활발히 사용 중입니다.

scripts/createComponent.ts 파일에서 CLI 인터페이스 구현을 위해 intro, outro, spinner, text, isCancel 등의 기능을 적극적으로 활용하고 있습니다. 해당 의존성은 필요한 패키지임이 확인되었습니다.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# @clack/prompts 패키지의 사용 여부 확인
rg -l "@clack/prompts"

Length of output: 77


Script:

#!/bin/bash
# scripts/createComponent.ts 파일에서 @clack/prompts의 사용 패턴 확인
cat scripts/createComponent.ts

Length of output: 3958

pnpm-workspace.yaml Show resolved Hide resolved
"@commitlint/cli": "^19.6.1",
"@commitlint/config-conventional": "^19.6.0",
"@commitlint/cz-commitlint": "^19.6.1",
"@commitlint/types": "^19.5.0",
"@clack/prompts": "^0.9.0",
"@storybook/addon-docs": "^8.4.7",
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

스토리북 패키지 버전 관리 방식을 통일해주세요.

일부 스토리북 패키지는 특정 버전(^8.4.7)을 사용하고 있고, 다른 패키지들은 catalog:를 참조하고 있습니다. 패키지 버전 관리 방식을 통일하여 유지보수성을 높이는 것이 좋습니다.

-    "@storybook/addon-docs": "^8.4.7",
+    "@storybook/addon-docs": "catalog:",
-    "@storybook/manager-api": "^8.4.7",
+    "@storybook/manager-api": "catalog:",
-    "@storybook/theming": "^8.4.7",
+    "@storybook/theming": "catalog:",

Also applies to: 26-26, 30-30

Copy link
Collaborator

@noahluftyang noahluftyang left a comment

Choose a reason for hiding this comment

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

LGTM!

@froggy1014 froggy1014 linked an issue Jan 12, 2025 that may be closed by this pull request
@froggy1014 froggy1014 merged commit e19885f into main Jan 12, 2025
6 of 7 checks passed
@froggy1014 froggy1014 deleted the chore/storybook-theme branch January 12, 2025 09:15
kimdaeyeobbb pushed a commit that referenced this pull request Jan 26, 2025
* chore(asset): add favicon, logo assets

* chore(storybook): add theme, manager storybook core API, Components

* style(storybook): add sipe branding in storybook

* style(storybook): add favicon

* chore(storybook): add addon-docs, react, react-dom for storybook mdx

* docs(storybook): add introduction mdx

* docs(storybook): rename concept -> intro

* docs(storybook): add category for all components

* chore(storybook): remove react and react-dom dependencies

* style(storybook): update secondary color and selected bar color

* chore(asset): rename sipe logo file

* chore(storybook): update brandImage file path

* chore(storybook): remove unused style
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Storybook Branding
2 participants