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

796 - refactor: Change gray colors palette #805

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

oibioib
Copy link
Collaborator

@oibioib oibioib commented Mar 2, 2025

What type of PR is this? (select all that apply)

  • πŸ• Feature
  • πŸ› Bug Fix
  • 🚧 Breaking Change
  • πŸ§‘β€πŸ’» Code Refactor
  • πŸ“ Documentation Update

Description

Redefine the gray color constants according to the Material Design palette. And name the colors variables as color-gray-xxx.

Related Tickets & Documents

Screenshots, Recordings

gray-palette

Added/updated tests?

  • πŸ‘Œ Yes
  • πŸ™…β€β™‚οΈ No, because they aren't needed
  • πŸ™‹β€β™‚οΈ No, because I need help

[optional] Are there any post deployment tasks we need to perform?

[optional] What gif best describes this PR or how it makes you feel?

Additional notes

When I was working on this issue, I discovered:

  1. In src/core/styles/_constants.scss there is a variable that is not used anywhere.
// Link color
$color-blue: hsl(202deg 89% 65%);
  1. The file /site/readme/styleguide-design.md must be updated according to the changes made.

  2. In src/core/styles/_constants.scss there is a comment:

// In case of updating any of these variables, please update the viewports.ts file inside e2e/utils folder

But there isn't such file or directory

Summary by CodeRabbit

Summary by CodeRabbit

  • New Features

    • Expanded the design palette with a comprehensive set of new gray shades, enabling more nuanced style choices and improved visual differentiation. These enhancements offer designers broader aesthetic options.
  • Style

    • Standardized the color presentation for technology themes by converting color codes to uniform lowercase, ensuring a consistent and polished look across the user interface.

Copy link
Contributor

coderabbitai bot commented Mar 2, 2025

πŸ“ Walkthrough

Walkthrough

The changes introduce a new section in the SCSS constants for gray colors, adding multiple variables that define various shades of gray using HSL values. Additionally, the hexadecimal color codes for existing technology theme variables (JavaScript, React, Angular, Node, AWS) have been modified to lowercase. These updates enhance the color palette available for styling without altering any application logic or control flow.

Changes

File Change Summary
src/core/styles/_constants.scss Added new gray color variables ($color-gray-900 to $color-gray-50) with HSL values; updated tech theme color variables to use lowercase hex codes

Suggested labels

preview

Suggested reviewers

  • andron13
  • dzmitry-varabei
  • natanchik
  • Wystov
  • Quiddlee
  • ansivgit
  • SpaNb4

πŸ“œ Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between 67cf40e and 31c88b4.

πŸ“’ Files selected for processing (1)
  • src/core/styles/_constants.scss (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/core/styles/_constants.scss

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.
  • @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.

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
Contributor

@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)
src/core/styles/_constants.scss (1)

77-78: Review Unused Variable.
The $color-blue variable designated for link color does not appear to be used. Consider removing it to clean up the codebase if it's not referenced elsewhere.

πŸ“œ Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between 58aee91 and 67cf40e.

πŸ“’ Files selected for processing (1)
  • src/core/styles/_constants.scss (1 hunks)
πŸ”‡ Additional comments (2)
src/core/styles/_constants.scss (2)

50-61: Material Gray Palette Implementation.
The new gray color variables are clearly defined with HSL values and follow a consistent naming convention aligned with Material Design guidelines. This enhances clarity and maintainability.


66-75: Consistent Technology Theme Colors.
The hexadecimal codes for the technology-themed color variables are now in lowercase, which improves consistency and readability. Great job refining these values!

@YulikK
Copy link
Collaborator

YulikK commented Mar 2, 2025

run visual now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Change gray colors palette to Material Design palette
3 participants