Skip to content

feat(dialog-select): [dialog-select] add attribute lock-scroll #3489

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

Merged
merged 1 commit into from
Jun 10, 2025

Conversation

James-9696
Copy link
Collaborator

@James-9696 James-9696 commented Jun 9, 2025

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
    • Added a new property to dialog select components that allows users to control whether scrolling is locked when the dialog is open.
  • Documentation
    • Updated demo descriptions to explain the new scroll locking option.
  • Tests
    • Added tests to verify scroll locking behavior when the dialog is opened.

Copy link

coderabbitai bot commented Jun 9, 2025

Walkthrough

A new lock-scroll (or lockScroll) boolean prop was introduced to the dialog-select component, defaulting to true. This prop allows users to control whether scroll locking is enabled when the dialog is open. The prop was documented, wired through component layers, and demonstrated in example usages and tests.

Changes

File(s) Change Summary
packages/vue/src/dialog-select/src/index.ts, .../src/pc.vue, .../demos/apis/dialog-select.js Added lockScroll/lock-scroll boolean prop (default true) to component and API docs
examples/sites/demos/pc/app/dialog-select/nest-grid-multi.vue, .../nest-grid-multi-composition-api.vue Bound :lock-scroll="false" to <tiny-dialog-select> in demo templates
examples/sites/demos/pc/app/dialog-select/nest-grid-multi.spec.ts Added test asserting scroll lock class is not present when dialog is opened with lock-scroll=false
examples/sites/demos/pc/app/dialog-select/webdoc/dialog-select.js Updated documentation to describe the lock-scroll attribute in demo explanations

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant DialogSelect
    participant DialogBox

    User->>DialogSelect: Open dialog (with lockScroll prop)
    DialogSelect->>DialogBox: Render with lock-scroll = lockScroll
    alt lockScroll = true
        DialogBox->>Document: Add scroll lock class to body
    else lockScroll = false
        DialogBox->>Document: Do not add scroll lock class
    end
Loading

Poem

A scroll lock switch now hops in place,
Dialogs open with gentle grace.
Set it true or set it not,
The page may scroll or may stay caught.
With tests and docs, the change is clear—
Hopping forward, year by year!
🐇✨

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.

examples/sites/demos/apis/dialog-select.js

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.

examples/sites/demos/pc/app/dialog-select/nest-grid-multi-composition-api.vue

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.

examples/sites/demos/pc/app/dialog-select/nest-grid-multi.vue

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.

  • 4 others
✨ 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 enhancement New feature or request (功能增强) label Jun 9, 2025
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: 1

🧹 Nitpick comments (1)
examples/sites/demos/pc/app/dialog-select/nest-grid-multi.spec.ts (1)

9-9: Consider adding a wait condition for dialog visibility.

The assertion checks for the absence of the scroll-lock class immediately after clicking the button. While this appears correct for the lock-scroll="false" case, consider adding a wait condition to ensure the dialog has fully opened before making the assertion, as dialog opening might involve asynchronous operations.

  await demo.getByRole('button', { name: '打开窗口' }).click()
+ await expect(page.locator('.tiny-dialog-box')).toBeVisible()
  await expect(page.locator('body')).not.toHaveClass(/dialog-box__scroll-lock/)
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 1e33249 and c85a7e2.

📒 Files selected for processing (7)
  • examples/sites/demos/apis/dialog-select.js (1 hunks)
  • examples/sites/demos/pc/app/dialog-select/nest-grid-multi-composition-api.vue (1 hunks)
  • examples/sites/demos/pc/app/dialog-select/nest-grid-multi.spec.ts (1 hunks)
  • examples/sites/demos/pc/app/dialog-select/nest-grid-multi.vue (1 hunks)
  • examples/sites/demos/pc/app/dialog-select/webdoc/dialog-select.js (1 hunks)
  • packages/vue/src/dialog-select/src/index.ts (1 hunks)
  • packages/vue/src/dialog-select/src/pc.vue (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: PR E2E Test (pnpm test:e2e3)
🔇 Additional comments (6)
examples/sites/demos/pc/app/dialog-select/nest-grid-multi.vue (1)

27-27: LGTM! Clean implementation of the lock-scroll feature.

The property binding correctly demonstrates the new lock-scroll feature by explicitly setting it to false. This follows Vue.js conventions for prop naming (kebab-case in templates, camelCase in JavaScript).

examples/sites/demos/pc/app/dialog-select/nest-grid-multi-composition-api.vue (1)

27-27: LGTM! Consistent implementation across API styles.

The lock-scroll property binding is correctly implemented and maintains consistency with the options API demo version. This ensures both Vue.js API styles demonstrate the feature properly.

packages/vue/src/dialog-select/src/index.ts (1)

86-88:

✅ Verification successful

LGTM! Proper prop implementation with backward compatibility.

The lockScroll prop is correctly implemented with:

  • Proper TypeScript typing (Boolean)
  • Sensible default value (true) that maintains backward compatibility
  • Standard camelCase naming convention

Let me verify that this prop is properly wired through to the template:


🏁 Script executed:

#!/bin/bash
# Description: Verify that the lockScroll prop is used in the PC template
# Expected: The prop should be passed to the dialog-box component

# Search for lockScroll usage in the pc.vue template
ast-grep --pattern 'lock-scroll'

# Also check for any camelCase usage
ast-grep --pattern 'lockScroll'

Length of output: 64


I’m not seeing any occurrences in the initial AST search. Let’s try a broader grep across all Vue templates:


🏁 Script executed:

#!/bin/bash
# Search for lockScroll usage in any .vue file
rg -n "lockScroll" --glob "*.vue"
rg -n "lock-scroll" --glob "*.vue"

Length of output: 6116


Verified lockScroll prop wiring

The lockScroll prop is correctly declared and passed through in the PC template:

  • In packages/vue/src/dialog-select/src/pc.vue (line 17):
    :lock-scroll="lockScroll"

No further changes needed.

packages/vue/src/dialog-select/src/pc.vue (1)

17-17: LGTM! Correct template binding.

The kebab-case binding :lock-scroll="lockScroll" follows Vue.js conventions and correctly passes the prop to the underlying dialog-box component.

examples/sites/demos/apis/dialog-select.js (1)

34-47: LGTM! Well-documented API addition.

The lock-scroll prop documentation is comprehensive with:

  • Correct type definition (boolean)
  • Appropriate default value (true)
  • Clear descriptions in both languages
  • Proper meta information indicating stability since 3.24.0
  • Consistent demo reference
examples/sites/demos/pc/app/dialog-select/webdoc/dialog-select.js (1)

15-17: LGTM! Clear documentation enhancement.

The updated documentation clearly explains the lock-scroll attribute functionality in both languages, helping users understand when and how to use this feature to control scrollbar behavior in popup dialogs.

Comment on lines +220 to +221
'mainHeight',
'lockScroll'
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Add prop definition with type and default value.

The prop should be defined with proper type and default value to match the API documentation which specifies boolean type with default true.

Replace the string-based prop definition with an object-based definition:

-    'mainHeight',
-    'lockScroll'
+    'mainHeight',
+    {
+      name: 'lockScroll',
+      type: Boolean,
+      default: true
+    }

Or alternatively, define all props using the object syntax for better type safety and consistency.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
'mainHeight',
'lockScroll'
'mainHeight',
{
name: 'lockScroll',
type: Boolean,
default: true
}
🤖 Prompt for AI Agents
In packages/vue/src/dialog-select/src/pc.vue at lines 220 to 221, the props
'mainHeight' and 'lockScroll' are currently defined as strings without type or
default values. Update the prop definitions to use the object syntax, specifying
the type as Boolean and setting the default value to true, to align with the API
documentation and improve type safety and consistency.

@zzcr zzcr merged commit 626ac2b into dev Jun 10, 2025
8 of 11 checks passed
@zzcr zzcr deleted the feat-dialog-select-props branch June 10, 2025 01:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request (功能增强)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants