fix: update splitMaterial and buildMaterials path

[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

更新 splitMaterials 与 buildMaterials 物料构建命令的路径。

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

• Chores
  • Updated asset and mock data source paths to align with the new directory structure.
• Bug Fixes
  • Enhanced error handling to warn users when necessary files are missing and suggest corrective actions.

[coderabbitai]

Walkthrough

This pull request updates file paths in two scripts that handle material assets. In buildMaterials.mjs, the paths for bundle.json and appinfo.json are changed to new directory locations. Additionally, error handling in the generateComponents function is enhanced with a check for missing files in the materials directory and a corresponding warning message. In splitMaterials.mjs, the file path for the bundle.json is similarly updated. There are no alterations to any public or exported entities.

Changes

Files	Summary
scripts/buildMaterials.mjs, scripts/splitMaterials.mjs	Updated file path for bundle.json from '/packages/design-core/public/mock/bundle.json' to '/designer-demo/public/mock/bundle.json'.
scripts/buildMaterials.mjs	Updated appinfo.json file path from '/mockServer/src/services/appinfo.json' to '/mockServer/src/assets/json/appinfo.json' and enhanced error handling with a file existence check that logs a warning if no files are found.

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant GC as generateComponents
    participant FS as File System
    participant L as Logger

    U->>GC: Initiate component generation
    GC->>FS: Check for files in materialsDir
    alt Files found
        GC->>GC: Process files
        alt Incorrect file format
            GC->>L: Log error message
        end
    else No files found
        GC->>L: Log warning to execute split materials command
    end

Loading

Possibly related PRs

• fix: self import change to relative import path #654: Addresses a similar update to the bundle.json file path in the material assets.
• fix: element-plus 物料适配问题修复与文档补充 #841: Involves modifications to the file path for material assets, directly related to this change.
• fix: fix materials panel #909: Similar update for loading the material asset bundle, reflecting a close code-level connection.

Suggested labels

bug, refactor-main

Suggested reviewers

• hexqi

Poem

I hop through the lines of code with glee,
Adjusting paths so all files roam free.
A warning chirps when files are lost,
In this revised garden, none shall cost.
With joyful hops, I debug the night—
Carrot-powered code shining bright! 🐰

Tip

🌐 Web search-backed reviews and chat

• We have enabled web search-based reviews and chat for all users. This feature allows CodeRabbit to access the latest documentation and information on the web.
• You can disable this feature by setting web_search: false in the knowledge_base settings.
• Please share any feedback in the Discord discussion.

---

📜 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 22a525d and 75b65c3.

📒 Files selected for processing (2)

• scripts/buildMaterials.mjs (1 hunks)
• scripts/splitMaterials.mjs (1 hunks)

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

• GitHub Check: push-check

🔇 Additional comments (3)

scripts/splitMaterials.mjs (1)

8-8: Verify the new bundle.json path exists.

The path change from /packages/design-core/public/mock/bundle.json to /designer-demo/public/mock/bundle.json aligns with the PR objectives. However, we should verify that the new path exists and is accessible.

Run the following script to verify the path:

✅ Verification successful

🏁 Script executed:

#!/bin/bash
# Description: Verify that the new bundle.json path exists and is accessible.

# Test: Check if the new path exists
if [ -f "designer-demo/public/mock/bundle.json" ]; then
  echo "✅ New path exists: designer-demo/public/mock/bundle.json"
else
  echo "❌ New path does not exist: designer-demo/public/mock/bundle.json"
fi

# Test: Check if the old path still exists (might indicate incomplete migration)
if [ -f "packages/design-core/public/mock/bundle.json" ]; then
  echo "⚠️ Old path still exists: packages/design-core/public/mock/bundle.json"
fi

Length of output: 231

---

Bundle.json path verification confirmed

The shell script execution confirmed that the new bundle.json exists at designer-demo/public/mock/bundle.json and the old file at packages/design-core/public/mock/bundle.json was not found.

scripts/buildMaterials.mjs (2)

12-12: Verify the new bundle.json path exists.

The path change from /packages/design-core/public/mock/bundle.json to /designer-demo/public/mock/bundle.json aligns with the PR objectives and is consistent with the change in splitMaterials.mjs.

---

14-14: Verify the new appinfo.json path and its dependencies.

The path change from /mockServer/src/services/appinfo.json to /mockServer/src/assets/json/appinfo.json needs verification.

Run the following script to verify the path and check for any other files that might be affected:

✅ Verification successful

🏁 Script executed:

#!/bin/bash
# Description: Verify the new appinfo.json path and check for dependencies.

# Test: Check if the new path exists
if [ -f "mockServer/src/assets/json/appinfo.json" ]; then
  echo "✅ New path exists: mockServer/src/assets/json/appinfo.json"
else
  echo "❌ New path does not exist: mockServer/src/assets/json/appinfo.json"
fi

# Test: Check if the old path still exists (might indicate incomplete migration)
if [ -f "mockServer/src/services/appinfo.json" ]; then
  echo "⚠️ Old path still exists: mockServer/src/services/appinfo.json"
fi

# Test: Search for any other files that might reference the old path
echo "Searching for files that might reference the old path..."
rg -l "services/appinfo.json"

Length of output: 382

---

Verified: The new appinfo.json path and its dependencies are correctly updated.

• The new file exists at mockServer/src/assets/json/appinfo.json.
• The old path mockServer/src/services/appinfo.json does not exist.
• No references to the old path were found in the codebase.

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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.