fix(material): add missing componentsMap to mockServer #700

[chilingling]

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: #700

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

Summary by CodeRabbit

• New Features

  • Introduced new components: TinyCheckbox, TinyCollapse, TinyCollapseItem, TinyBreadcrumb, and TinyBreadcrumbItem to enhance application functionality.
  • Enabled destructuring for multiple components, improving usability and flexibility during integration.

• Improvements

  • Updated the exportName for a previously defined package, indicating a rebranding.
  • Modified the structure of the options property for TinyBreadcrumb for better definition and processing.
  • Adjusted the data type of active property in TinyTimeLine for improved logic interpretation.

[coderabbitai]

Walkthrough

The recent changes enhance the JSON schemas for component definitions, particularly for the @opentiny/vue package and the element-plus library. New components have been added with improved destructuring capabilities, while existing configurations have been updated for better usability and flexibility. These modifications reflect a modern approach to component design, aiming to improve integration and configuration in applications.

Changes

Files	Change Summary
mockServer/src/mock/get/app-center/v1/apps/schema/918.json	Added new components for @opentiny/vue: TinyCheckbox, TinyCollapse, TinyCollapseItem, TinyBreadcrumb, and TinyBreadcrumbItem, all with destructuring: true and version 3.14.0.
packages/design-core/public/mock/bundle.json	Enhanced element-plus components with destructuring: true for several components and changed exportName from "Select" to "Breadcrumb". Modified TinyBreadcrumb schema and updated active property in TinyTimeLine from string to number.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant App
    participant TinyComponents

    User->>App: Import components
    App->>TinyComponents: Request TinyCheckbox, TinyCollapse, etc.
    TinyComponents-->>App: Provide component definitions
    App-->>User: Components available for use

Loading

🐇 In a world of code where rabbits play,
New components hop in, brightening the day!
TinyCheckbox and Breadcrumb, so neat,
With destructuring magic, they can’t be beat.
Hooray for the changes, let’s frolic and cheer,
For a whimsical codebase, full of joy and cheer! 🥳

---

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.

[coderabbitai]

Actionable comments posted: 0

Outside diff range, codebase verification and nitpick comments (1)

packages/design-core/public/mock/bundle.json (1)

8910-8912: The exportName change from Select to Breadcrumb has not been consistently applied.

There are still multiple occurrences of the old exportName "Select" in the following files:

• mockServer/src/mock/get/app-center/v1/apps/schema/918.json
• mockServer/src/services/appinfo.json
• mockServer/assets/json/bundle.json
• packages/vue-generator/test/testcases/sfc/case01/componentsMap.json
• packages/design-core/public/mock/bundle.json

Please ensure that all occurrences of the old exportName are updated to "Breadcrumb" to maintain consistency and avoid potential issues.

Analysis chain

Verify the exportName change from Select to Breadcrumb.

Ensure that this change aligns with the intended functionality and does not introduce any breaking changes.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the `exportName` change from `Select` to `Breadcrumb`.

# Test: Search for the `exportName` usage. Expect: Only occurrences of the new `exportName`.
rg --type json -A 5 $'"exportName": "Breadcrumb"'

Length of output: 1007

---

Script:

#!/bin/bash
# Description: Verify if there are any remaining occurrences of the old `exportName` "Select".

# Test: Search for the old `exportName`. Expect: No occurrences of the old `exportName`.
rg --type json -A 5 $'"exportName": "Select"'

Length of output: 3466

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between fd164a1 and a89db3c.

Files selected for processing (2)

• mockServer/src/mock/get/app-center/v1/apps/schema/918.json (2 hunks)
• packages/design-core/public/mock/bundle.json (9 hunks)

Additional comments not posted (13)

mockServer/src/mock/get/app-center/v1/apps/schema/918.json (5)

1922-1926: LGTM! New component definition for TinyCheckbox is correct.

The new component definition is consistent with other component definitions.

---

1985-1989: LGTM! New component definition for TinyCollapse is correct.

The new component definition is consistent with other component definitions.

---

1992-1996: LGTM! New component definition for TinyCollapseItem is correct.

The new component definition is consistent with other component definitions.

---

1999-2003: LGTM! New component definition for TinyBreadcrumb is correct.

The new component definition is consistent with other component definitions.

---

2006-2010: LGTM! New component definition for TinyBreadcrumbItem is correct.

The new component definition is consistent with other component definitions.

packages/design-core/public/mock/bundle.json (8)

26-27: LGTM! Destructuring import for ElInput enhances usability.

The addition of "destructuring": true for ElInput is a good improvement.

---

307-308: LGTM! Destructuring import for ElButton enhances usability.

The addition of "destructuring": true for ElButton is a good improvement.

---

629-630: LGTM! Destructuring import for ElForm enhances usability.

The addition of "destructuring": true for ElForm is a good improvement.

---

1087-1088: LGTM! Destructuring import for ElFormItem enhances usability.

The addition of "destructuring": true for ElFormItem is a good improvement.

---

1438-1439: LGTM! Destructuring import for ElTable enhances usability.

The addition of "destructuring": true for ElTable is a good improvement.

---

2677-2678: LGTM! Destructuring import for ElTableColumn enhances usability.

The addition of "destructuring": true for ElTableColumn is a good improvement.

---

14016-14019: LGTM! Enhanced schema for TinyBreadcrumb improves option definition and processing.

The modification to the TinyBreadcrumb schema is a good improvement.

---

14274-14275: LGTM! Correct type usage for active property in TinyTimeLine.

Changing the active property from a string to a number ensures correct type usage.