feat：elementplus 物料更新

[Dive12300]

English | 简体中文

PR

PR Checklist

Please check if your PR fulfills the following requirements:

• [x] 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)
• [x] 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
• [x] No

Other information

Summary by CodeRabbit

• New Features

  • Introduced a comprehensive configuration for the Vue framework with centralized component definitions and usage examples.
  • Added a utility for generating structured JSON data from the Element Plus component library, streamlining access to component information.
  • Implemented a detailed configuration for the ElButton component, enhancing customization options for developers.

• Chores

  • Added new dependencies to support HTTP requests and HTML parsing.
  • Improved packaging and schema management for better integration of UI components.

• Documentation

  • Included example snippets for using new components within Vue templates.

[coderabbitai[bot]]

Walkthrough

This update enhances the Vue framework integration by introducing a new bundle_new.json for the ElButton component configuration and a utility script to generate structured component data from the Element Plus documentation. The changes focus on improving component management and streamlining the development process.

Changes

File(s)	Change Summary
bundle.json, packages/design-core/public/mock/bundle_new.json	Introduced comprehensive configuration for Vue components using Element Plus, detailing UI components with attributes and providing usage snippets for ElButton.
packages/.../genMeterials.js	New file automates JSON data generation from Element Plus documentation, utilizing axios and cheerio.
packages/vue-generator/.../package.json	Downgraded vite-plugin-static-copy version, possibly for compatibility reasons.
packages/vue-generator/src/generator/vue/sfc/generateAttribute.js	Updated string interpolation for Vue template compatibility in handleSlotBindAttrHook.
packages/vue-generator/src/plugins/genGlobalState.js	Improved string value handling in genDependenciesPlugin, enhancing robustness.
packages/vue-generator/test/testcases/.../index.js	Added export for testState to enhance state management.
packages/vue-generator/test/testcases/.../testState.js	New Pinia store with state, getters, and actions for managing application data.
packages/vue-generator/test/testcases/.../mockData.js	Expanded globalState structure for enhanced state management capabilities.
packages/vue-generator/test/testcases/sfc/case06/...	Introduced multiple new test files and JSON mapping for the TinyTree component, validating component generation.
packages/vue-generator/vite.config.mjs	Updated test configuration to exclude node_modules from testing.
scripts/buildMaterials.mjs	Enhanced material management by integrating application schema data and component mappings.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant genMeterials.js
    participant ElementPlusAPI
    participant bundle_new.json

    Developer->>genMeterials.js: Initiate data generation
    genMeterials.js->>ElementPlusAPI: Fetch component data
    ElementPlusAPI-->>genMeterials.js: Return component details
    genMeterials.js->>bundle_new.json: Generate and save JSON structure
    Developer-->>bundle_new.json: Review component configuration

🐰 In the meadow where bunnies play,
New changes hop in, bright as day!
With buttons and snippets, oh what fun,
Vue's magic grows, we’re on the run!
State management's smart, our code is neat,
Let's build our dreams, with joy, not defeat! 🌼

---

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

[hexqi]

需要对所有commit添加签名，签名后commit后会有一个Verified的小绿标，如何对提交签名可以搜索下，这块教程很多

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

You need to add a signature to all commits. After signing, there will be a small green mark of Verified after the commit. You can search for how to sign the commit. There are many tutorials on this topic.