-
Notifications
You must be signed in to change notification settings - Fork 264
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(design): the path is incorrect #2433
Conversation
WalkthroughThe changes involve updating the import path for the Changes
Suggested labels
Poem
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 (
|
[e2e-test-warn] 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 |
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.
Actionable comments posted: 1
🧹 Outside diff range and nitpick comments (2)
packages/design/aurora/index.ts (2)
30-30
: Consider the implications of cross-design system dependencies.Moving components between design systems (aurora → saas) could lead to:
- Inconsistent styling if the design systems have different visual languages
- Maintenance challenges due to cross-system dependencies
- Potential circular dependencies between design systems
Consider either:
- Keeping the component in aurora if it's integral to aurora's design system
- Moving all dependent components to saas if this component truly belongs there
- Creating a shared component library if this component is used across multiple design systems
30-30
: Update documentation to reflect the component's new location.Since this is a structural change in the design system, ensure that:
- Component documentation reflects its new location
- Design system documentation is updated if this represents a significant architectural change
@@ -27,7 +27,7 @@ import Pager from './src/pager' | |||
import Wizard from './src/wizard' | |||
import DialogBox from './src/dialog-box' | |||
import Popeditor from './src/popeditor' | |||
import DialogSelect from './src/dialog-select' | |||
import DialogSelect from '../saas/src/dialog-select' |
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.
💡 Codebase verification
Invalid import path detected - component location mismatch
The import path ../saas/src/dialog-select
in packages/design/aurora/index.ts
is incorrect as:
- The
packages/saas
directory does not exist - The actual DialogSelect component is located in
packages/design/saas/src/dialog-select
The correct import path should be ../design/saas/src/dialog-select
or a relative path that properly points to the component in the packages/design/saas
directory.
🔗 Analysis chain
Verify the component exists in the new location.
The import path has been changed to reference the DialogSelect component from the saas design system instead of the local aurora system.
Let's verify the component exists in the new location and there are no other references to the old path:
Let me gather more information to verify the component's existence and references.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Verify the component exists in the new location
fd "dialog-select" "packages/saas/src"
# Check for any remaining references to the old path
rg -g "!*.{log,md}" "src/dialog-select" "packages/design/aurora"
Length of output: 289
Script:
#!/bin/bash
# Search for dialog-select files across the entire repository
fd "dialog-select" .
# Search for any imports of dialog-select component
rg -g "!*.{log,md}" "import.*DialogSelect" .
# Check if packages/saas directory exists and list its contents
ls -la packages/saas 2>/dev/null || echo "packages/saas directory not found"
Length of output: 1984
@@ -27,7 +27,7 @@ import Pager from './src/pager' | |||
import Wizard from './src/wizard' | |||
import DialogBox from './src/dialog-box' | |||
import Popeditor from './src/popeditor' | |||
import DialogSelect from './src/dialog-select' | |||
import DialogSelect from '../saas/src/dialog-select' |
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.
这个应该需要删除的,我已在release-3.19.0分支提交了哈
PR
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information
Summary by CodeRabbit
DialogSelect
component to improve module dependency structure.