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

feat: update template #572

Merged
merged 1 commit into from
Jun 11, 2024

Conversation

hexqi
Copy link
Collaborator

@hexqi hexqi commented Jun 11, 2024

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 new environment configuration files for alpha, development, and production modes.
    • Added a basic HTML template for the Design Core Preview.
    • Introduced a custom input configurator component.
    • Added new Vite configuration for the project.
  • Refactor

    • Updated paths and imports for configurators and source directories.
    • Removed unnecessary imports and commands from the engine CLI index file.
    • Updated canvas.js to use new import methods and setup.
  • Enhancements

    • Improved initialization logic for TinyEngine framework components and configurations.
    • Updated registry configuration to include additional settings and tools.

Copy link
Contributor

coderabbitai bot commented Jun 11, 2024

Walkthrough

The updates across various files primarily focus on refining the structure and functionality of the designer-demo and engine-cli packages. Key changes include modifying import paths, updating environment configurations, and introducing new files for better modularity and clarity. These changes aim to enhance the setup and initialization processes for the TinyEngine framework, streamline build and development workflows, and improve the configurability of the design tool.

Changes

File/Directory Path Change Summary
designer-demo/src/main.js Updated import statement for configurators from './configurators.js' to './configurators/'.
packages/engine-cli/src/commands/create.js Modified source directory path to include designer subdirectory.
packages/engine-cli/src/index.js Removed imports for fs, globby, path, chalk, and commands serve and build.
packages/engine-cli/template/designer/canvas.html Updated the src attribute of a <script> tag to use an absolute path.
packages/engine-cli/template/designer/env/.env.alpha, .env.development, .env.production Introduced new environment configuration files for different modes.
packages/engine-cli/template/designer/package.json Added new package.json with project configurations and dependencies.
packages/engine-cli/template/designer/preview.html Introduced a basic HTML template for Design Core Preview.
packages/engine-cli/template/designer/registry.js Added configuration object with various settings for the designer tool.
packages/engine-cli/template/designer/src/canvas.js Updated imports and application setup logic.
packages/engine-cli/template/designer/src/configurators/MyInputConfigurator.vue Introduced a custom input configurator component.
packages/engine-cli/template/designer/src/configurators/index.js Imported and exported configurator components.
packages/engine-cli/template/designer/src/defineEntry.js Updated copyright year and exported registry object.
packages/engine-cli/template/designer/src/main.js Introduced logic for initializing components and configurations for TinyEngine framework.
packages/engine-cli/template/designer/src/preview.js Updated to use initPreview from @opentiny/tiny-engine.
packages/engine-cli/template/designer/vite.config.js Introduced logic to define Vite configuration for the project.

Poem

In the realm of code so bright,
Paths and imports set just right.
Configs for the alpha, dev, and prod,
TinyEngine's setup, we applaud.
New tools and scripts, all aligned,
A designer's dream, now refined.
🐇✨🚀


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

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: 1

Outside diff range and nitpick comments (2)
packages/engine-cli/src/index.js (1)

11-11: Consider adding an English translation for the command description to enhance accessibility for non-Chinese speaking developers.

packages/engine-cli/template/designer/src/configurators/MyInputConfigurator.vue (1)

30-32: Document the dataType prop to clarify its usage and expected values.

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 2bc0e42 and 218db8e.

Files ignored due to path filters (1)
  • packages/engine-cli/template/designer/public/favicon.ico is excluded by !**/*.ico
Files selected for processing (17)
  • designer-demo/src/main.js (1 hunks)
  • packages/engine-cli/src/commands/create.js (1 hunks)
  • packages/engine-cli/src/index.js (1 hunks)
  • packages/engine-cli/template/designer/canvas.html (1 hunks)
  • packages/engine-cli/template/designer/env/.env.alpha (1 hunks)
  • packages/engine-cli/template/designer/env/.env.development (1 hunks)
  • packages/engine-cli/template/designer/env/.env.production (1 hunks)
  • packages/engine-cli/template/designer/package.json (1 hunks)
  • packages/engine-cli/template/designer/preview.html (1 hunks)
  • packages/engine-cli/template/designer/registry.js (1 hunks)
  • packages/engine-cli/template/designer/src/canvas.js (2 hunks)
  • packages/engine-cli/template/designer/src/configurators/MyInputConfigurator.vue (1 hunks)
  • packages/engine-cli/template/designer/src/configurators/index.js (1 hunks)
  • packages/engine-cli/template/designer/src/defineEntry.js (2 hunks)
  • packages/engine-cli/template/designer/src/main.js (1 hunks)
  • packages/engine-cli/template/designer/src/preview.js (2 hunks)
  • packages/engine-cli/template/designer/vite.config.js (1 hunks)
Files skipped from review due to trivial changes (9)
  • packages/engine-cli/template/designer/canvas.html
  • packages/engine-cli/template/designer/env/.env.alpha
  • packages/engine-cli/template/designer/env/.env.development
  • packages/engine-cli/template/designer/env/.env.production
  • packages/engine-cli/template/designer/package.json
  • packages/engine-cli/template/designer/preview.html
  • packages/engine-cli/template/designer/registry.js
  • packages/engine-cli/template/designer/src/configurators/index.js
  • packages/engine-cli/template/designer/src/defineEntry.js
Additional comments not posted (10)
packages/engine-cli/template/designer/src/canvas.js (2)

13-13: LGTM! The import statement correctly imports createRender from @opentiny/tiny-engine/canvas.


15-15: Ensure window.parent.TinyGlobalConfig is securely handled to prevent cross-origin issues.

packages/engine-cli/template/designer/src/preview.js (1)

13-13: LGTM! The import statement correctly imports initPreview from @opentiny/tiny-engine.

packages/engine-cli/template/designer/vite.config.js (3)

1-2: LGTM! The import statements are correctly set up for the Vite configuration.


5-21: The configuration setup is well-structured and effectively uses environment variables. Good job on maintaining clarity and modularity.


5-22: The export of the configuration function is correctly implemented.

packages/engine-cli/src/index.js (1)

Line range hint 1-1: LGTM! The import statements are correctly set up for the CLI functionality.

designer-demo/src/main.js (1)

17-17: Ensure ./configurators/ contains an index.js that exports modules correctly.

Verification successful

Verify the usage of configurators in the codebase to ensure the import path change does not introduce any issues.


The configurators import path change appears to be correctly integrated and used across multiple files in the codebase without any issues.

  • designer-demo/src/main.js
  • packages/engine-cli/template/designer/src/main.js
  • packages/entry/src/configurators.js
  • packages/entry/src/index.js
  • packages/design-core/src/registerConfigurators.js
  • packages/design-core/src/init.js

The index.js file in the configurators directory correctly exports the necessary modules, and the usage of configurators in the codebase aligns with the new import path.

Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify the existence and correctness of index.js in the configurators directory.

# Test: Check if index.js exists and contains export statements.
fd index.js designer-demo/src/configurators/ --exec cat {}

Length of output: 366



Script:

#!/bin/bash
# Description: Verify the usage of configurators in the codebase.

# Search for usage of configurators in the codebase.
rg 'configurators' --glob '!designer-demo/src/configurators/index.js'

Length of output: 1399

packages/engine-cli/src/commands/create.js (1)

24-24: Verify the existence of the designer subdirectory in the template directory.

Verification successful

The designer subdirectory exists in the template directory, confirming that the updated source path is correct.

Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify the existence of the designer subdirectory in the template directory.

# Test: Check if the designer directory exists.
fd designer packages/engine-cli/template/ --exec ls -l {}

Length of output: 602

packages/engine-cli/template/designer/src/main.js (1)

17-17: Ensure ./configurators/ contains an index.js that exports modules correctly.

Verification successful

The index.js file in the configurators directory correctly exports the necessary modules.

  • packages/engine-cli/template/designer/src/configurators/index.js
Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify the existence and correctness of index.js in the configurators directory.

# Test: Check if index.js exists and contains export statements.
fd index.js packages/engine-cli/template/designer/src/configurators/ --exec cat {}

Length of output: 390

@chilingling chilingling merged commit 4e6064e into opentiny:refactor/develop Jun 11, 2024
yy-wow pushed a commit to yy-wow/tiny-engine that referenced this pull request Oct 10, 2024
@coderabbitai coderabbitai bot mentioned this pull request Jan 25, 2025
14 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants