Skip to content

Conversation

@JinUng41
Copy link
Collaborator

@JinUng41 JinUng41 commented Apr 8, 2025

  • BFX, DNF는 색상 제외 / 현재 디자인 시스템에 반영되어 있지 않음.

👻 PULL REQUEST

📄 작업 내용

  • 디자인 시스템을 반영하여, 색상을 추가하고 폴더링을 진행하였습니다.
  • 현재 디자인 시스템에서 BFX와 DNF는 팀 색상이 구현되어 있지 않아, 반영하지 않았습니다.

🔗 연결된 이슈

Summary by CodeRabbit

  • New Features
    • Introduced an expanded suite of color palettes that enhance the visual consistency and overall design of the application.
    • These refined color themes provide a richer, cohesive interface experience across all device types.

- BFX, DNF는 색상 제외 / 현재 디자인 시스템에 반영되어 있지 않음.
@JinUng41 JinUng41 added the 🧀 add 사진 등 에셋이나 라이브러리 또는 빈 파일 추가 시 사용 label Apr 8, 2025
@JinUng41 JinUng41 added this to the 리팩토링 마감 milestone Apr 8, 2025
@JinUng41 JinUng41 requested a review from youz2me April 8, 2025 07:01
@JinUng41 JinUng41 self-assigned this Apr 8, 2025
@coderabbitai
Copy link

coderabbitai bot commented Apr 8, 2025

Walkthrough

This pull request introduces multiple new JSON files to the iOS asset catalog. These files, placed in various directories under Wable-iOS/Resource/Color.xcassets/, contain metadata and color definitions. The JSON structures include an info object with properties such as author set to "xcode" and version set to 1. Several files also define specific color sets with sRGB components and a universal idiom.

Changes

Files Change Summary
Wable-iOS/Resource/Color.xcassets/{GrayScale, Primary, Secondary, System, Team}/Contents.json Added metadata JSON files to define asset catalog information (author: "xcode", version: 1).
Wable-iOS/Resource/Color.xcassets/Secondary/{blue10, blue50}.colorset/Contents.json Introduced new secondary color set definitions with specified sRGB components.
Wable-iOS/Resource/Color.xcassets/Team/{bro10, bro50, dk10, dk50, drx10, drx50, gen10, gen50, hle10, hle50, kt10, kt50, ns10, ns50, t110, t150}.colorset/Contents.json Added multiple Team-specific color sets with defined sRGB components and a universal idiom.

Assessment against linked issues

Objective Addressed Explanation
디자인 시스템 기반 색상 추가 [#162]

Poem

I’m a tiny bunny, hopping in the code,
New colors now brightly on the road.
Each JSON file sings a cheerful tune,
With Xcode’s magic under the moon.
I skip through assets with a joyful cheer—
Coding delights, oh so dear! 🐇


🪧 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.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai plan to trigger planning for file edits and PR creation.
  • @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
Member

@youz2me youz2me left a comment

Choose a reason for hiding this comment

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

고생하셨습니닷

@github-project-automation github-project-automation bot moved this to In Review in Wable-iOS Apr 8, 2025
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: 0

🧹 Nitpick comments (1)
Wable-iOS/Resource/Color.xcassets/Team/bro10.colorset/Contents.json (1)

1-21: Ensure JSON Validity & Consistency
The JSON structure for the "bro10" color set is correctly defined with its color components and metadata. Please verify that the hexadecimal values (e.g., "0xFA", "0xEB") accurately reflect the intended design system colors. Additionally, it appears there is an extraneous line ("21") following the closing brace—please confirm this is not unintentional and remove it if necessary.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between c40ab52 and 51c51bf.

📒 Files selected for processing (23)
  • Wable-iOS/Resource/Color.xcassets/GrayScale/Contents.json (1 hunks)
  • Wable-iOS/Resource/Color.xcassets/Primary/Contents.json (1 hunks)
  • Wable-iOS/Resource/Color.xcassets/Secondary/Contents.json (1 hunks)
  • Wable-iOS/Resource/Color.xcassets/Secondary/blue10.colorset/Contents.json (1 hunks)
  • Wable-iOS/Resource/Color.xcassets/Secondary/blue50.colorset/Contents.json (1 hunks)
  • Wable-iOS/Resource/Color.xcassets/System/Contents.json (1 hunks)
  • Wable-iOS/Resource/Color.xcassets/Team/Contents.json (1 hunks)
  • Wable-iOS/Resource/Color.xcassets/Team/bro10.colorset/Contents.json (1 hunks)
  • Wable-iOS/Resource/Color.xcassets/Team/bro50.colorset/Contents.json (1 hunks)
  • Wable-iOS/Resource/Color.xcassets/Team/dk10.colorset/Contents.json (1 hunks)
  • Wable-iOS/Resource/Color.xcassets/Team/dk50.colorset/Contents.json (1 hunks)
  • Wable-iOS/Resource/Color.xcassets/Team/drx10.colorset/Contents.json (1 hunks)
  • Wable-iOS/Resource/Color.xcassets/Team/drx50.colorset/Contents.json (1 hunks)
  • Wable-iOS/Resource/Color.xcassets/Team/gen10.colorset/Contents.json (1 hunks)
  • Wable-iOS/Resource/Color.xcassets/Team/gen50.colorset/Contents.json (1 hunks)
  • Wable-iOS/Resource/Color.xcassets/Team/hle10.colorset/Contents.json (1 hunks)
  • Wable-iOS/Resource/Color.xcassets/Team/hle50.colorset/Contents.json (1 hunks)
  • Wable-iOS/Resource/Color.xcassets/Team/kt10.colorset/Contents.json (1 hunks)
  • Wable-iOS/Resource/Color.xcassets/Team/kt50.colorset/Contents.json (1 hunks)
  • Wable-iOS/Resource/Color.xcassets/Team/ns10.colorset/Contents.json (1 hunks)
  • Wable-iOS/Resource/Color.xcassets/Team/ns50.colorset/Contents.json (1 hunks)
  • Wable-iOS/Resource/Color.xcassets/Team/t110.colorset/Contents.json (1 hunks)
  • Wable-iOS/Resource/Color.xcassets/Team/t150.colorset/Contents.json (1 hunks)
🔇 Additional comments (22)
Wable-iOS/Resource/Color.xcassets/Primary/Contents.json (1)

1-7: Valid Metadata for Primary Colors
The metadata file is concise and follows the standard structure with an "info" object containing "author" and "version". This is consistent with the design system requirements and similar asset catalog files.

Wable-iOS/Resource/Color.xcassets/System/Contents.json (1)

1-7: Proper Metadata for System Colors
This JSON file provides the necessary asset catalog metadata with the correct "info" properties. It aligns well with the other asset catalog files in the project.

Wable-iOS/Resource/Color.xcassets/Secondary/Contents.json (1)

1-7: Consistent Metadata for Secondary Colors
The file maintains consistency by defining the "info" object with "author": "xcode" and "version": 1. This structure is in line with other similar metadata files added to the project.

Wable-iOS/Resource/Color.xcassets/GrayScale/Contents.json (1)

1-7: Accurate GrayScale Asset Metadata
The JSON structure here is correctly formatted, containing the required "info" object. Consistency across all asset catalog metadata files is evident, which supports maintainability with the design system updates.

Wable-iOS/Resource/Color.xcassets/Team/Contents.json (1)

1-6: JSON Metadata File is correctly structured.

The file uses the standard asset catalog metadata format with an "info" object containing the "author" and "version" keys. It meets the design system specifications.

Wable-iOS/Resource/Color.xcassets/Team/ns50.colorset/Contents.json (1)

1-21: Valid Color Set Definition for ns50.

The color set is well-defined with the proper "colors" array, color-space declaration, color components (using hex strings), and a universal idiom. The metadata section is also appropriately structured.

Wable-iOS/Resource/Color.xcassets/Team/dk10.colorset/Contents.json (1)

1-21: Proper Color Set Format for dk10.

The file correctly defines the color components (with expected hex values and full opacity) and includes the necessary "info" metadata. This adheres to the expected asset catalog conventions.

Wable-iOS/Resource/Color.xcassets/Team/kt50.colorset/Contents.json (1)

1-21: Consistent and Accurate Color Set Definition for kt50.

The JSON clearly specifies the sRGB color with its components and sets the idiom to "universal". The metadata is correctly added, ensuring consistency with other asset catalog files.

Wable-iOS/Resource/Color.xcassets/Team/bro50.colorset/Contents.json (1)

1-21: Clear and Correct Definition for bro50 Color Set.

This file defines the color set in line with the design system format. All color components are provided using the expected hexadecimal notation, and the metadata is complete.

Wable-iOS/Resource/Color.xcassets/Team/drx10.colorset/Contents.json (1)

1-20: Approved: drx10 color set JSON structure adheres to the design system.
The JSON structure is well-formed with the correct sRGB color components (red: 0xE4, green: 0xE3, blue: 0xF3) and appropriate metadata. This file is consistent with Xcode’s asset catalog format.

Wable-iOS/Resource/Color.xcassets/Secondary/blue10.colorset/Contents.json (1)

1-20: Approved: blue10 color set JSON is correctly configured.
The file defines the expected color components (red: 0xEF, green: 0xF5, blue: 0xFD) and includes the standard metadata. It aligns perfectly with the design system requirements.

Wable-iOS/Resource/Color.xcassets/Team/gen50.colorset/Contents.json (1)

1-20: Approved: gen50 color set JSON is correctly structured.
The asset shows the proper sRGB specification with matching component values (red: 0xAA, green: 0x8B, blue: 0x30) and metadata. It maintains the consistency observed across the new color files.

Wable-iOS/Resource/Color.xcassets/Team/kt10.colorset/Contents.json (1)

1-20: Approved: kt10 color set JSON displays the expected sRGB components and metadata.
The file correctly specifies red (0xFC), green (0xE4), and blue (0xE4) with full opacity via the alpha component. It meets the design system’s standards and matches the structure of the other new assets.

Wable-iOS/Resource/Color.xcassets/Team/hle10.colorset/Contents.json (1)

1-20: Approved: hle10 color set JSON is complete and valid.
The JSON defines the color with the proper components (red: 0xFB, green: 0xEE, blue: 0xE6) and metadata, conforming to the asset catalog specifications and design system guidelines.

Wable-iOS/Resource/Color.xcassets/Team/t150.colorset/Contents.json (1)

1-20: New Team Color Set (t150) is well-structured.
The JSON file correctly defines the color using the sRGB color space with the proper hexadecimal components and includes the mandatory metadata. This aligns with the design system requirements outlined in the PR.

Wable-iOS/Resource/Color.xcassets/Secondary/blue50.colorset/Contents.json (1)

1-20: Secondary Color Set (blue50) is defined correctly.
The file follows the standard format for color assets with all necessary keys (colors array, color-space, components, idiom, and info) and uses the proper hexadecimal values. The structure is consistent with other similar color files in the project.

Wable-iOS/Resource/Color.xcassets/Team/ns10.colorset/Contents.json (1)

1-20: Team Color Set (ns10) is complete and compliant.
The JSON properly encapsulates the color components and metadata. The choice of identical hexadecimal values for each channel (0xE3) is correctly represented, and the universal idiom is appropriately applied.

Wable-iOS/Resource/Color.xcassets/Team/dk50.colorset/Contents.json (1)

1-20: Team Color Set (dk50) JSON file is accurate.
All the required fields are present and correctly formatted. The RGBA components (with 0x4F for red, 0x55 for green, and 0x51 for blue) and the metadata conform with the project’s design system expectations.

Wable-iOS/Resource/Color.xcassets/Team/t110.colorset/Contents.json (1)

1-20: Team Color Set (t110) is implemented correctly.
The file accurately defines the color with the specified RGBA components and includes the correct "info" metadata. It meets the design system criteria and integrates smoothly with the other newly added color assets.

Wable-iOS/Resource/Color.xcassets/Team/gen10.colorset/Contents.json (1)

1-21: Valid JSON structure and adherence to the design system.
The JSON file correctly defines a color set using the expected keys (“colors”, “color-space”, “components”, “idiom”, and “info”). The hex values (red: "0xF4", green: "0xF1", blue: "0xE8") and the alpha value ("1.000") are formatted consistently with the other assets. Please double-check that these specific color values align with the latest design specifications.

Wable-iOS/Resource/Color.xcassets/Team/hle50.colorset/Contents.json (1)

1-21: New color asset “hle50.colorset” is correctly defined.
The file follows the established JSON structure and metadata conventions (using sRGB, defining “components” with appropriate hex values, and marking the idiom as "universal"). Please confirm with the design team that the chosen values (red: "0xF4", green: "0x73", blue: "0x20", alpha: "1.000") are final.

Wable-iOS/Resource/Color.xcassets/Team/drx50.colorset/Contents.json (1)

1-21: “drx50.colorset” asset is formatted as expected.
The JSON file properly encapsulates the new color definition including the sRGB components (red: "0x10", green: "0x04", blue: "0xA4", alpha: "1.000") and the required metadata. Ensure that these values meet the intended design guidelines and that similar files in the project remain consistent with this formatting approach.

@JinUng41 JinUng41 merged commit 67b6df2 into develop Apr 8, 2025
1 check passed
@github-project-automation github-project-automation bot moved this from In Review to Done in Wable-iOS Apr 8, 2025
@JinUng41 JinUng41 deleted the add/#162-design-system-color branch April 8, 2025 07:04
youz2me pushed a commit that referenced this pull request Oct 26, 2025
[Add] 디자인 시스템을 반영한 색상 추가
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🧀 add 사진 등 에셋이나 라이브러리 또는 빈 파일 추가 시 사용

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

[Add] 디자인 시스템 기반 색상 추가

3 participants