-
Notifications
You must be signed in to change notification settings - Fork 354
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix/mock utils axios cdn link #1062
Fix/mock utils axios cdn link #1062
Conversation
WalkthroughThis pull request involves a comprehensive version update across multiple packages from version Changes
Sequence DiagramsequenceDiagram
participant Dev as Developer
participant Workflow as Release Workflow
participant Packages as Project Packages
Dev->>Workflow: Trigger Release
Workflow->>Packages: Update Versions
Workflow->>Packages: Validate Package Configurations
Workflow->>Packages: Generate Release Artifacts
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (61)
✅ Files skipped from review due to trivial changes (49)
🔇 Additional comments (13)
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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Caution
Inline review comments failed to post. This is likely due to GitHub's limits when posting large numbers of comments.
Actionable comments posted: 3
🧹 Nitpick comments (2)
packages/canvas/route-bar/src/CanvasRouteBar.vue (1)
77-78
: Consider adding English comments for better international collaboration.- .replace(/\/+/g, '/') // 替换连续的 '/' 为单个 '/' - .replace(/^\/|\/$/g, ''), // 去掉开头和结尾的 '/' + .replace(/\/+/g, '/') // Replace consecutive '/' with single '/' + .replace(/^\/|\/$/g, ''), // Remove leading and trailing '/'packages/engine-cli/template/designer/public/mock/bundle.json (1)
Line range hint
1-14037
: Consider using dynamic version resolution for component schemas.The component schemas have hardcoded version numbers in their configurations. Consider making these versions dynamic by referencing the consolidated package versions from the new "packages" section.
Example refactor for component version references:
{ "version": "2.4.2", // Hardcoded version "npm": { "package": "element-plus", - "version": "2.4.2" + "version": "${packages['element-plus'].version}" } }
🛑 Comments failed to post (3)
packages/toolbars/refresh/package.json (1)
3-3: 💡 Codebase verification
Changelog documentation needed for version 2.2.0-rc.0
The version bump to 2.2.0-rc.0 warrants documentation of changes, but no changelog entries were found at either package or root level. Consider:
- Adding a CHANGELOG.md in the package directory
- Or updating the root CHANGELOG.md with the new version's changes
🔗 Analysis chain
Consider documenting breaking changes if any.
The version bump to
2.2.0-rc.0
indicates a release candidate with potential new features. While the PR description mentions no breaking changes, it's good practice to document any significant changes or new features in the changelog.🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Check for CHANGELOG.md updates fd "CHANGELOG.md" --exec cat {} \; | grep -A 5 "2.2.0-rc.0"Length of output: 60
Script:
#!/bin/bash # Check if CHANGELOG.md exists and show its content if found echo "=== Checking for CHANGELOG.md in package directory ===" cat packages/toolbars/refresh/CHANGELOG.md 2>/dev/null || echo "CHANGELOG.md not found in package directory" echo -e "\n=== Checking package directory content ===" ls -la packages/toolbars/refresh/ echo -e "\n=== Looking for any changelog files in the package ===" fd "CHANGELOG" packages/toolbars/refresh/Length of output: 976
Script:
#!/bin/bash # Check root level CHANGELOG.md echo "=== Checking root CHANGELOG.md ===" cat CHANGELOG.md 2>/dev/null || echo "No root CHANGELOG.md found" echo -e "\n=== Checking package.json diff ===" git diff HEAD^1 packages/toolbars/refresh/package.json || echo "No diff found"Length of output: 335
packages/settings/props/package.json (1)
3-3: 💡 Codebase verification
Update @vueuse/core from ^9.6.0 to ^12.4.0
The current version is significantly behind the latest release. Since the project uses Vue 3.4.15 and modern build tools, updating to the latest version is recommended. Please test thoroughly after the update due to the major version difference.
🔗 Analysis chain
Update @vueuse/core dependency.
While updating to
2.2.0-rc.0
, consider updating the fixed dependency on@vueuse/core@^9.6.0
to a newer version for potential bug fixes and improvements.🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Check latest version of @vueuse/core curl -s "https://registry.npmjs.org/@vueuse/core/latest" | jq '.version'Length of output: 79
Script:
#!/bin/bash # Check current @vueuse/core version and package.json content cat packages/settings/props/package.jsonLength of output: 1266
packages/engine-cli/template/designer/public/mock/bundle.json (1)
14038-14054: 💡 Codebase verification
⚠️ Package versions are significantly outdated and need updates
- element-plus (2.4.2 → 2.9.3): ~5 minor versions behind
- @opentiny/vue (3.14.0 → 3.21.1): ~7 minor versions behind
Consider implementing a version update strategy to maintain security and feature parity. The CDN configuration is secure but references outdated versions.
🔗 Analysis chain
Verify the package versions and CDN links for security concerns.
The newly added "packages" section consolidates library configurations, but the hardcoded CDN links and versions need verification:
- [email protected]
- @opentiny/vue@~3.14.0
Run the following script to check for security advisories and latest versions:
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Check for security advisories and latest versions # Check NPM for latest versions echo "Checking latest versions..." npm view element-plus version npm view @opentiny/vue version # Check for security advisories echo "Checking security advisories..." npm audit [email protected] npm audit @opentiny/[email protected] # Verify CDN availability and response echo "Verifying CDN links..." curl -I https://unpkg.com/[email protected]/dist/index.full.mjs curl -I https://unpkg.com/@opentiny/vue@~3.14/runtime/tiny-vue.mjsLength of output: 2813
English | 简体中文
PR
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
Background and solution
What is the current behavior?
本地启动mock服务有报错

Issue Number: N/A
What is the new behavior?
正常加载utils,无报错
Does this PR introduce a breaking change?
Other information
Summary by CodeRabbit
/browse/
segment