feat: registry add themes

[hexqi]

English | 简体中文

PR

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our Commit Message Guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)
• Built its own designer, fully self-validated

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

Background and solution

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

Summary by CodeRabbit

• New Features

  • Introduced dynamic theme loading with support for light and dark themes.
  • Added configuration for multiple themes, allowing users to switch between light and dark modes.

• Chores

  • Updated build and development scripts to use cross-env for setting environment variables.

[coderabbitai]

Walkthrough

The recent changes introduce dynamic theme support in the designer-demo and design-core projects. The VITE_THEME environment variable is used to switch between light and dark themes. This includes updates to configuration files, script commands, and the addition of the cross-env package for setting environment variables. The changes ensure that the correct theme is loaded based on the environment configuration, enhancing flexibility and user experience.

Changes

File(s)	Change Summary
designer-demo/package.json	Updated dev and build scripts to use cross-env for setting VITE_THEME. Added cross-env as a dev dependency.
designer-demo/registry.js	Added themes array with light and dark theme objects. Modified theme property to fetch from import.meta.env.VITE_THEME.
designer-demo/src/main.js	Added import statement for @opentiny/tiny-engine-theme.
designer-demo/vite.config.js	Added conditional resolution for @opentiny/tiny-engine-theme based on VITE_THEME.
packages/design-core/registry.js	Added themes array with light and dark theme objects.
packages/design-core/src/init.js	Commented out an import statement related to loading a theme style based on a configuration parameter.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Env as Environment
    participant App as Application
    participant ThemeManager as Theme Manager

    User->>Env: Set VITE_THEME
    Env->>App: Provide VITE_THEME value
    App->>ThemeManager: Load theme based on VITE_THEME
    ThemeManager->>App: Apply selected theme
    App->>User: Display themed application

Loading

Poem

In code's bright light, a theme does change,
From dark to light, a seamless range.
With cross-env's magic, the scripts now sing,
A dynamic theme, a wondrous thing.
The registry holds both dark and light,
For every user's delight.
🌟✨

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 5636b85 and 1fa3bdb.

Files selected for processing (6)

• designer-demo/package.json (2 hunks)
• designer-demo/registry.js (1 hunks)
• designer-demo/src/main.js (1 hunks)
• designer-demo/vite.config.js (2 hunks)
• packages/design-core/registry.js (1 hunks)
• packages/design-core/src/init.js (1 hunks)

Files skipped from review due to trivial changes (2)

• designer-demo/src/main.js
• packages/design-core/src/init.js

Additional comments not posted (6)

designer-demo/package.json (2)

7-8: The use of cross-env for setting environment variables enhances cross-platform compatibility.

---

22-22: Adding cross-env as a development dependency is appropriate for the functionality of the modified scripts.

designer-demo/registry.js (2)

48-48: Using import.meta.env.VITE_THEME for dynamic theme selection aligns with modern JavaScript practices.

---

54-61: The addition of the themes array is well-structured and enhances theme configuration options.

packages/design-core/registry.js (1)

70-79: The addition of the themes array with titles enhances user-friendliness and theme management.

designer-demo/vite.config.js (1)

65-68: The conditional resolution for the theme package based on the VITE_THEME environment variable is correctly implemented and ensures dynamic theme loading.