feat: add package of opentiny/tiny-engine-theme-base

[James-9696]

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 @opentiny/tiny-engine-theme-base, providing a comprehensive base theme with light and dark variations.
  • Added new theme configuration files to support the base theme library.

• Enhancements

  • Updated design-core to use the new tinyEngineThemeLight theme.

• Style

  • Standardized margin styling across various components for consistent layout and spacing.

• Dependencies

  • Added @opentiny/tiny-engine-theme-base as a dependency in design-core.

[coderabbitai]

Walkthrough

This update introduces a new theme system for the project, including base styling within the @opentiny/tiny-engine-theme-base package. Key changes include the addition and importation of theme dependencies, adjustments to CSS styling across various components for consistency, and updates to configuration files to integrate the new theme.

Changes

Files/Paths	Change Summary
packages/build/vite-config/src/vite-plugins/devAliasPlugin.js	Added alias for @opentiny/tiny-engine-theme-base
packages/design-core/package.json	Added dependency for @opentiny/tiny-engine-theme-base
packages/design-core/src/init.js	Updated theme import from tinySmbTheme to tinyEngineThemeLight
Multiple .vue files across different packages	Adjusted margin styling to margin: 0; for better layout and spacing consistency
packages/theme/base/**	Introduced new theme files defining base theme, light, and dark components including Vite configuration

Sequence Diagram(s)

N/A

Poem

In the land of code so bright,
A theme emerged, both dark and light.
With colors bold and margins neat,
Our design evolved, a tidy feat.
Thanks to base and light's delight,
Our project shines in day and night.
🐇🌈✨

Tip

AI model upgrade

gpt-4o model for reviews and chat is now live

OpenAI claims that this model is better at understanding and generating code than the previous models. Please join our Discord Community to provide any feedback or to report any issues.

---

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 0c71520 and d6763c6.

Files selected for processing (13)

• packages/build/vite-config/src/vite-plugins/devAliasPlugin.js (1 hunks)
• packages/design-core/package.json (1 hunks)
• packages/design-core/src/init.js (2 hunks)
• packages/layout/src/DesignSettings.vue (1 hunks)
• packages/plugins/bridge/src/Main.vue (1 hunks)
• packages/plugins/materials/src/meta/layout/src/Main.vue (1 hunks)
• packages/settings/panel/src/Main.vue (1 hunks)
• packages/theme/base/package.json (1 hunks)
• packages/theme/base/src/base.js (1 hunks)
• packages/theme/base/src/dark-component.js (1 hunks)
• packages/theme/base/src/index.js (1 hunks)
• packages/theme/base/src/light-component.js (1 hunks)
• packages/theme/base/vite.config.js (1 hunks)

Files skipped from review due to trivial changes (8)

• packages/build/vite-config/src/vite-plugins/devAliasPlugin.js
• packages/design-core/package.json
• packages/layout/src/DesignSettings.vue
• packages/plugins/bridge/src/Main.vue
• packages/plugins/materials/src/meta/layout/src/Main.vue
• packages/settings/panel/src/Main.vue
• packages/theme/base/package.json
• packages/theme/base/vite.config.js

Additional comments not posted (9)

packages/theme/base/src/index.js (3)

1-1: Import statement looks good.

The import statement correctly imports the necessary theme components from base.js.

---

3-8: LGTM! Ensure consistency in theme naming conventions.

The tinyEngineThemeLight object is well-structured and follows a consistent naming convention. Verify that the id, name, and cnName fields align with the project's standards.

---

10-15: LGTM! Ensure consistency in theme naming conventions.

The tinyEngineThemeDark object is well-structured and follows a consistent naming convention. Verify that the id, name, and cnName fields align with the project's standards.

packages/theme/base/src/light-component.js (1)

1-19: LGTM! Ensure all necessary theme properties are included.

The concatThemeLight object is well-structured and includes various theme properties for light mode. Verify that all necessary properties are included and correctly defined.

packages/theme/base/src/dark-component.js (1)

1-19: LGTM! Ensure all necessary theme properties are included.

The concatThemeDark object is well-structured and includes various theme properties for dark mode. Verify that all necessary properties are included and correctly defined.

packages/design-core/src/init.js (2)

20-20: Import statement looks good.

The import statement correctly imports the tinyEngineThemeLight from @opentiny/tiny-engine-theme-base.

---

55-55: LGTM! Ensure proper initialization of the theme.

The theme initialization with TinyThemeTool and tinyEngineThemeLight is well-structured. Verify that the initialization aligns with the project's standards.

packages/theme/base/src/base.js (2)

1-297: LGTM! Ensure all necessary base theme properties are included.

The tinyBaseTheme object is well-structured and includes various base theme properties. Verify that all necessary properties are included and correctly defined.

---

299-301: Export statements look good.

The export statements correctly export the light and dark components.