Skip to content

Conversation

@zzcr
Copy link
Member

@zzcr zzcr commented Apr 23, 2025

fix(picker): 增强日期选择器在移动端和PC端的兼容性,添加isPCMode参数以控制显示逻辑

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)

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:

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

  • New Features

    • Improved picker component behavior to allow PC-style picker display on mobile screens when PC mode is enabled.
  • Bug Fixes

    • Picker visibility now accurately responds to PC mode settings across different device types, ensuring consistent user experience.

…nd PC, add isPCMode parameter to control the display logic
@coderabbitai
Copy link

coderabbitai bot commented Apr 23, 2025

Walkthrough

This update introduces an isPCMode parameter to the picker component's core logic, affecting how pickers are displayed on mobile and PC screens. The watchPickerVisible and handleFocus functions now consider the isPCMode flag to determine whether to show PC-style pickers on mobile devices. The propagation of this flag is achieved by updating the function signatures and ensuring it is passed through the component's initialization process. Minor formatting adjustments and clarifying comments are also included, but no other functional changes are present.

Changes

File(s) Change Summary
packages/renderless/src/picker/index.ts Added isPCMode parameter to watchPickerVisible and handleFocus; updated logic to allow PC picker on mobile if isPCMode is true; minor formatting and comments.
packages/renderless/src/picker/vue.ts Updated initApi and renderless signatures to accept and propagate isPCMode; passed isPCMode to relevant API methods.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant PickerComponent
    participant API

    User->>PickerComponent: Focuses input
    PickerComponent->>API: handleFocus({ ..., isPCMode })
    API->>PickerComponent: Determines picker type
    alt isPCMode true or not mobile
        PickerComponent->>PickerComponent: Show PC-style picker
    else
        PickerComponent->>PickerComponent: Show mobile picker
    end
Loading

Poem

A rabbit hopped on mobile ground,
"Should I show the picker, or PC mode abound?"
With isPCMode in paw, it checks the scene,
Now pickers appear where they've never been seen!
A tweak, a hop, a logic delight—
Pickers for all, from morning till night!
🐇✨

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

packages/renderless/src/picker/index.ts

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the plugin "eslint-plugin-vue".

(The package "eslint-plugin-vue" was not found when loaded as a Node module from the directory "".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

npm install eslint-plugin-vue@latest --save-dev

The plugin "eslint-plugin-vue" was referenced from the config file in ".eslintrc.js » @antfu/eslint-config » @antfu/eslint-config-vue".

If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team.

packages/renderless/src/picker/vue.ts

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the plugin "eslint-plugin-vue".

(The package "eslint-plugin-vue" was not found when loaded as a Node module from the directory "".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

npm install eslint-plugin-vue@latest --save-dev

The plugin "eslint-plugin-vue" was referenced from the config file in ".eslintrc.js » @antfu/eslint-config » @antfu/eslint-config-vue".

If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team.

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

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.

@github-actions github-actions bot added the bug Something isn't working label Apr 23, 2025
@petercat-assistant
Copy link

Walkthrough

This PR enhances the compatibility of the date picker for both mobile and PC platforms by introducing an isPCMode parameter. This parameter allows for control over the display logic, ensuring the date picker functions appropriately across different devices.

Changes

Files Summary
packages/renderless/src/picker/index.ts, packages/renderless/src/picker/vue.ts Added isPCMode parameter to functions to control display logic for date picker on mobile and PC. Adjusted logic to handle different screen types and picker visibility.

({ api, vm, dispatch, emit, props, state, nextTick, isPCMode }) =>
(value) => {
if (props.readonly || state.pickerDisabled || state.isMobileScreen) return
if (props.readonly || state.pickerDisabled || (state.isMobileScreen && !isPCMode)) return

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ensure that the isPCMode parameter is correctly passed and utilized in all relevant functions to avoid potential logic errors in determining picker visibility.

const api = {} as IPickerApi
const { reactive, computed, watch, onBeforeUnmount, inject, markRaw, onMounted } = hooks
const { vm, service, parent, useBreakpoint } = vnode
const { vm, service, parent, useBreakpoint, isPCMode } = vnode

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verify that isPCMode is consistently integrated into the API initialization to prevent any discrepancies in behavior across different devices.

@zzcr zzcr linked an issue Apr 23, 2025 that may be closed by this pull request
Copy link

@coderabbitai coderabbitai bot left a 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

🧹 Nitpick comments (1)
packages/renderless/src/picker/index.ts (1)

1073-1075: Consider removing unnecessary whitespace

There are extra blank lines that don't affect functionality but could be removed for consistency with the rest of the codebase.

  state.pickerVisible = state.picker.state.visible = visible

-
  api.emitInput(date, visible)
-

  state.date = date
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0cc6f28 and 970c76b.

📒 Files selected for processing (2)
  • packages/renderless/src/picker/index.ts (3 hunks)
  • packages/renderless/src/picker/vue.ts (4 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (1)
packages/renderless/src/picker/vue.ts (1)
packages/renderless/src/picker/index.ts (2)
  • handleFocus (942-968)
  • watchPickerVisible (66-93)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: PR E2E Test (pnpm test:e2e3)
🔇 Additional comments (9)
packages/renderless/src/picker/vue.ts (5)

179-179: Function signature updated to include isPCMode parameter

The initApi function now includes an isPCMode parameter, which will help control the picker's display behavior on mobile vs PC screens. This is aligned with the PR's objective of enhancing component compatibility across platforms.


193-193: Properly passing isPCMode to handleFocus

The isPCMode parameter is correctly forwarded to the handleFocus method, ensuring the mode preference is considered when the picker receives focus.


216-216: Properly passing isPCMode to watchPickerVisible

The isPCMode parameter is correctly forwarded to the watchPickerVisible method, which will allow conditional picker visibility based on the mode preference.


309-310: Extracting isPCMode from vnode

The isPCMode value is correctly extracted from the vnode object, making it available to the component's rendering logic.


316-316: Passing isPCMode to initApi

The isPCMode parameter is properly passed to the initApi function, ensuring the mode preference propagates through the component's API initialization.

packages/renderless/src/picker/index.ts (4)

66-69: Updated watchPickerVisible to honor isPCMode parameter

The watchPickerVisible function now properly considers the isPCMode flag when determining if the picker should be shown on mobile screens. This change enables consistent picker behavior across platforms when requested.


942-956: Enhanced handleFocus with isPCMode condition and improved comments

The handleFocus function now properly uses the isPCMode parameter to determine the picker display behavior on mobile screens. The added comments clearly explain the conditional logic, improving code readability and maintainability.


957-964: Improved comments for mobile date and time component conditions

The added comments clearly explain the different conditions for displaying date and time mobile components, which improves code readability.


1067-1067: Minor code formatting improvement

The code formatting has been improved for better readability.

@zzcr zzcr changed the title fix(picker): enhance the compatibility of the date picker on mobile and PC, add isPCMode parameter to control the display logic fix(picker): [date-picker]enhance the compatibility of the date picker on mobile and PC, add isPCMode parameter to control the display logic Apr 23, 2025
@kagol kagol merged commit 6a2fd6b into dev Apr 23, 2025
17 of 21 checks passed
@kagol kagol deleted the fix-date-picker-0423 branch April 23, 2025 07:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

🐛 [Bug]: 手机端日期选择器点击后没有弹出选择器

3 participants