[PE-244] fix: space app editor colors

[aaryan610]

Description

This PR adds the missing CSS variables for editor colors to the space app,

Type of Change

• Bug fix (non-breaking change which fixes an issue)

Summary by CodeRabbit

• Style
  • Enhanced editor color theming with new CSS variables for text and background colors
  • Added support for light and dark theme color variations
  • Introduced customizable color palette for different editor color categories

[coderabbitai]

Walkthrough

The pull request introduces a comprehensive set of CSS variables in the globals.css file to define editor color schemes. These variables cover text and background colors for various color categories including gray, peach, pink, orange, green, light blue, dark blue, and purple. The variables are designed to support both light and dark themes using data-theme attribute selectors, providing a flexible and customizable color palette for the editor's styling.

Changes

File	Change Summary
space/styles/globals.css	Added 16 new CSS variables for editor text and background colors across different color themes (gray, peach, pink, orange, green, light blue, dark blue, purple)

Suggested labels

🐛bug, 🎨UI / UX

Suggested reviewers

• pushya22

Possibly related PRs

• [PE-237] fix: editor placeholder and muted text color #6430: Modifies color properties for placeholder text in the editor
• [WEB-3045] fix: sticky placeholder, gray color value #6436: Updates background color for "gray" color in sticky editor

Poem

🎨 Colorful Coding Rabbit's Delight 🐰

In globals we dance, with colors so bright
Text and backgrounds, a thematic delight
Gray, peach, and pink, in themes light and dark
Our editor's palette leaves a vibrant mark!

• Your friendly CodeRabbit 🖌️

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

space/styles/globals.css (1)

317-327: Remove duplicated background color definitions.

The background colors defined in the root section are identical to those in the light theme section. Consider removing them from the root section to avoid duplication and potential maintenance issues.

  :root {
    /* text colors */
    --editor-colors-gray-text: #5c5e63;
    --editor-colors-peach-text: #ff5b59;
    --editor-colors-pink-text: #f65385;
    --editor-colors-orange-text: #fd9038;
    --editor-colors-green-text: #0fc27b;
    --editor-colors-light-blue-text: #17bee9;
    --editor-colors-dark-blue-text: #266df0;
    --editor-colors-purple-text: #9162f9;
    /* end text colors */

-   /* background colors */
-   --editor-colors-gray-background: #d6d6d8;
-   --editor-colors-peach-background: #ffd5d7;
-   --editor-colors-pink-background: #fdd4e3;
-   --editor-colors-orange-background: #ffe3cd;
-   --editor-colors-green-background: #c3f0de;
-   --editor-colors-light-blue-background: #c5eff9;
-   --editor-colors-dark-blue-background: #c9dafb;
-   --editor-colors-purple-background: #e3d8fd;
-   /* end background colors */
  }

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 586a320 and 1c90d2f.

📒 Files selected for processing (1)

• space/styles/globals.css (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: Analyze (javascript)
• GitHub Check: Analyze (python)

🔇 Additional comments (2)

space/styles/globals.css (2)

329-338: LGTM!

The light theme background colors are well-defined with appropriate pastel shades, and the selector correctly handles both light themes.

---

339-348: LGTM!

The dark theme background colors are well-defined with appropriate darker shades, and the selector correctly handles both dark themes.