-
Notifications
You must be signed in to change notification settings - Fork 321
fix(dialog-box): modify mobile dialog-box problem #2644
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
Conversation
WalkthroughThe changes introduced in this pull request focus on enhancing the dialog box component's visibility handling and interaction with the DOM. Key modifications include replacing references to Changes
Possibly related PRs
Suggested labels
Suggested reviewers
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: 0
🧹 Outside diff range and nitpick comments (3)
packages/mobile/components/dialog-box/src/renderless/index.ts (3)
88-88
: Architectural improvement: Using direct component referenceReplacing
parent.$el
withvm.$el
ensures direct access to the dialog-box's own element, which is more reliable than accessing through the parent component.
Line range hint
296-316
: Critical fix: Dialog drag functionalityThe changes to
handleDrag
fix potential issues with mobile dialog-box dragging by:
- Using direct component reference with
vm.$el
- Ensuring proper popover handling during drag operations
However, there's a potential issue:
- The function signature includes 'vm' in the Pick type but vm is not in the parameter list
Apply this fix to correct the function signature:
- ({ parent, props, state, emit }: Pick<IDialogBoxRenderlessParams, 'parent' | 'props' | 'state' | 'emit' | 'vm'>) => + ({ parent, props, state, emit, vm }: Pick<IDialogBoxRenderlessParams, 'parent' | 'props' | 'state' | 'emit' | 'vm'>) =>
Line range hint
1-365
: Add tests for the dialog-box changesThe PR objectives indicate that tests haven't been added for these changes. Given the critical nature of the dialog-box functionality in mobile views, tests should be added to verify:
- Proper element references using vm.$el
- Dialog dragging behavior
- Popover handling during drag operations
Would you like me to help generate test cases for these scenarios?
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (2)
packages/mobile/components/dialog-box/src/renderless/index.ts
(4 hunks)packages/mobile/components/input/src/input.ts
(2 hunks)
🔇 Additional comments (3)
packages/mobile/components/input/src/input.ts (2)
16-29
: LGTM: Import reorganization maintains functionality
The reorganization of imports from './renderless' improves code organization while maintaining the same functionality.
61-61
: Verify the necessity and usage of the new title prop
A new title
prop has been added, but its purpose and relationship to the dialog-box fix is unclear.
✅ Verification successful
Let me gather more specific information about the input component and its usage.
Let me check one more thing to understand how this title prop is being used in the component's template and related files.
Based on the verification results, I can now provide a final response:
The title prop is properly implemented and used in the mobile input component
The title prop is used to display a title section above the input field, as shown in the component's template:
<div class="tiny-mobile-input__title" v-if="slots.title || title">
<slot name="title">{{ title }}</slot>
</div>
This implementation allows for both prop-based and slot-based title rendering, which is a common pattern for mobile form inputs.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Search for usage of the title prop in the codebase
rg -l "title.*props" --type ts
Length of output: 281
Script:
#!/bin/bash
# Check the implementation and usage of title in input component
ast-grep --pattern 'title: $_'
# Check for input component usage with title prop
rg "title.*Input" -A 2 --type ts
# Check the actual input component implementation
cat packages/mobile/components/input/src/input.ts
Length of output: 6397
Script:
#!/bin/bash
# Check the template file for title usage
cat packages/mobile/components/input/src/*.vue
# Search for any references to input component's title in tests
rg "title.*input" -A 2 --type test
Length of output: 7248
packages/mobile/components/dialog-box/src/renderless/index.ts (1)
289-290
: Consistent component reference in closeAllPopover
Updated to use vm
instead of parent
for consistency with other changes and better component encapsulation.
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
New Features
title
property to the input component.Bug Fixes
Refactor