fix(chart): huiCharts打包替换为Chart

[Davont]

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)

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:

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

  • Updated component naming conventions in generated outputs, replacing 'Huicharts' with 'Chart' for improved clarity.

• Bug Fixes

  • Adjusted the handling of component names to ensure accurate aliasing in export statements.

[coderabbitai]

Walkthrough

The changes in this pull request primarily involve modifications to the build-entry.ts file, specifically in the getMainTemplate and createEntry functions. The updates focus on renaming components in the output templates, particularly replacing 'Huicharts' with 'Chart' in the export statements. This affects how components are referenced in the generated output while maintaining the overall structure and logic of the functions.

Changes

File Path	Change Summary
internals/cli/src/commands/build/build-entry.ts	Updated getMainTemplate and createEntry functions to replace 'Huicharts' with 'Chart' in component names for export statements.

Possibly related PRs

• build(charts): compatible with the old version of charts chart introd… #2327: Modifications to build-entry.ts regarding component name processing and exporting, directly related to the changes in createEntry.
• refactor(charts): [charts] rename chart-core packages to huicharts-core #2027: Involves renaming chart-related packages, aligning with the semantic changes from 'Huicharts' to 'Chart'.
• fix(chart): modify chart packages #2354: Changes to build-chart-theme.ts related to chart packages, indicating ongoing structural changes in charting.
• fix(chart): modify chart package #2365: Similar to fix(chart): modify chart packages #2354, focuses on theme naming conventions in build-chart-theme.ts, possibly connecting to overall chart component naming changes.

Suggested labels

bug

Suggested reviewers

• zzcr

🐰 In the meadow where charts bloom bright,
A name change brings forth new light.
From 'Hui' to 'Chart', we hop with glee,
Renaming components, as happy as can be!
With each export, a fresh start,
A joyful dance, a work of art! 🌼📊

---

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

[github-actions]

[e2e-test-warn]
The component to be tested is missing.

The title of the Pull request should look like "fix(vue-renderless): [action-menu, alert] fix xxx bug".

Please make sure you've read our contributing guide

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)

internals/cli/src/commands/build/build-entry.ts (1)

116-117: Consider adding a deprecation notice

The component renaming in defaultComponents matches the changes in exportComponents. Consider adding a deprecation notice in the documentation to help users migrate from 'Huicharts' to 'Chart'.

Would you like me to help draft a deprecation notice or migration guide for this breaking change?

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 277de36 and 3c3f4de.

📒 Files selected for processing (1)

• internals/cli/src/commands/build/build-entry.ts (2 hunks)

🔇 Additional comments (2)

internals/cli/src/commands/build/build-entry.ts (2)

106-107: Verify the component renaming impact

The replacement of 'Huicharts' with 'Chart' in the export aliases changes how these components can be imported. This could be a breaking change if other parts of the codebase are using the old naming convention.

Let's check for existing imports that might be affected:

---

106-107: Document version compatibility

Since this change modifies how components are exported and could affect imports, it should be properly versioned and documented.

Let's check the version bump and changelog:

Also applies to: 116-117