fix: preview failure

[lichunn]

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?

1、修复builtin-component包的组件预览不了问题
2、调整RadioGroupConfigurator组件间距

Does this PR introduce a breaking change?

• Yes
• No

Other information

Summary by CodeRabbit

Summary by CodeRabbit

• Chores

  • Updated import configuration for the @opentiny/tiny-engine-builtin-component package to use .mjs file extension, improving module compatibility.

• Style

  • Enhanced visual presentation of radio buttons by adding padding styles to the .meta-radio-group-container class.

[coderabbitai]

Walkthrough

The pull request modifies the import map configuration for the @opentiny/tiny-engine-builtin-component package by changing the file extension from .js to .mjs, indicating a shift towards ES module syntax. Additionally, the RadioGroupConfigurator.vue file is updated to include new CSS styles for the .meta-radio-group-container class, enhancing the visual presentation of radio buttons. These changes are localized to their respective files, aligning with modern JavaScript practices and improving component styling.

Changes

File	Change Summary
packages/design-core/src/preview/src/preview/importMap.json	Updated import path for @opentiny/tiny-engine-builtin-component from .js to .mjs extension
packages/configurator/src/radio-group-configurator/RadioGroupConfigurator.vue	Added new CSS styles for .meta-radio-group-container class to adjust padding for radio buttons

Possibly related PRs

• feat/buildin com mjs format #918: Changes the output file format for built-in components from .js to .mjs, directly related to the import map modification.
• fix(preview): fix designer-demo can't preview #554: Modifies the preview functionality that may interact with the import map configuration.
• fix: fix some issue on preview page #568: Updates the preview page and includes changes to script paths relevant to the import map adjustments.

Suggested labels

refactor-main

Suggested reviewers

• chilingling
• hexqi

Poem

🐰 A module's dance, from .js to .mjs
Hopping through imports with moduline bliss
ES modules sing, a technological kiss
Tiny Engine's path, now crystal clear
Rabbit's code leap brings modernization near! 🚀

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 14effcb and 84452c1.

📒 Files selected for processing (1)

• packages/configurator/src/radio-group-configurator/RadioGroupConfigurator.vue (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• packages/configurator/src/radio-group-configurator/RadioGroupConfigurator.vue

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

• GitHub Check: push-check

---

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

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b5789c5 and 7d211e6.

📒 Files selected for processing (1)

• packages/design-core/src/preview/src/preview/importMap.json (1 hunks)

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

• GitHub Check: push-check

🔇 Additional comments (1)

packages/design-core/src/preview/src/preview/importMap.json (1)

13-13: LGTM! The extension change to .mjs should fix the preview functionality.

The change aligns with ES module standards and matches the module format used by other dependencies in the import map.