Skip to content

feat(dialog-select): supports transparent transmission of selectAll, selectChange and radioChange events #3398

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
May 8, 2025

Conversation

zzcr
Copy link
Member

@zzcr zzcr commented May 8, 2025

feat(dialog-select): 支持透传selectAll、selectChange和radioChange事件

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
    • Event handlers for multi-grid selection and radio changes now provide additional details, including the table instance and event object, to external event callbacks. This allows for more comprehensive event handling in custom integrations.

Copy link

coderabbitai bot commented May 8, 2025

Walkthrough

The changes update the event handler signatures for multi-grid selection actions in the dialog-select module. Each handler now receives an additional $table parameter and the original event object, and conditionally invokes external event callbacks with these details if such callbacks are defined in the grid options.

Changes

File(s) Change Summary
packages/renderless/src/dialog-select/index.ts Updated signatures for multiGridSelectAll, multiGridSelectChange, and multiGridRadioChange to include $table and event parameters. Modified handlers to call corresponding event callbacks with updated arguments if defined in props.gridOp.events.

Poem

In the warren of code where the tables reside,
New paws pass $table and event side by side.
With callbacks now wiser, and handlers in sync,
The grid’s little secrets are shared in a blink.
A hop and a leap—selection flows free,
As rabbits and tables thrive in harmony! 🐇

Tip

⚡️ Faster reviews with caching
  • CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.

✨ 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.

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 May 8, 2025
Copy link

Walkthrough

This PR enhances the dialog-select component by adding support for transparent transmission of selectAll, selectChange, and radioChange events. This allows these events to be passed through and handled externally, providing more flexibility in event management.

Changes

File Summary
packages/renderless/src/dialog-select/index.ts Added support for transparent transmission of selectAll, selectChange, and radioChange events by modifying the respective functions to include event parameters and conditional event triggering.

@@ -61,7 +61,7 @@ export const queryGridData =

export const multiGridSelectAll =
({ api, props, state }) =>
({ selection, checked }) => {
({ selection, checked, $table }, event) => {

Choose a reason for hiding this comment

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

Ensure that the $table and event parameters are correctly passed and utilized in the event handlers to avoid potential runtime errors.

}

export const multiGridSelectChange =
({ api, props, state, vm }) =>
({ row, checked }) => {
({ row, checked, $table }, event) => {

Choose a reason for hiding this comment

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

Ensure that the $table and event parameters are correctly passed and utilized in the event handlers to avoid potential runtime errors.

@@ -567,10 +577,15 @@ export const multiTreeRadio =

export const multiGridRadioChange =
({ props, state }) =>
({ row }) => {
({ row, $table }, event) => {

Choose a reason for hiding this comment

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

Ensure that the $table and event parameters are correctly passed and utilized in the event handlers to avoid potential runtime errors.

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 (2)
packages/renderless/src/dialog-select/index.ts (2)

62-95: Good implementation of transparent event propagation.

The multiGridSelectAll handler now correctly forwards both the $table reference and the original event object to the external handler. This enhancement properly implements the "transparent transmission" feature mentioned in the PR title.

One suggestion to consider:

-    // 透传配置式表格selectAll事件
+    // 透传配置式表格selectAll事件 - Transparently transmit the table selectAll event with original event object and table reference
     if (props.gridOp?.events?.selectAll) {
       props.gridOp.events.selectAll({ selection, checked, $table }, event)
     }

97-143: Consistent implementation of event forwarding.

The changes to multiGridSelectChange follow the same pattern as multiGridSelectAll, ensuring consistent behavior across the component.

Consider documenting the parameter changes in a JSDoc comment for better developer experience:

 export const multiGridSelectChange =
   ({ api, props, state, vm }) =>
+  /**
+   * Handles selection changes in the multi-grid component
+   * @param {Object} params - Selection change parameters
+   * @param {Object} params.row - The row that was selected/deselected
+   * @param {boolean} params.checked - Whether the row was selected or deselected
+   * @param {Object} params.$table - Reference to the table instance
+   * @param {Event} event - The original DOM event
+   */
   ({ row, checked, $table }, event) => {
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 8a72dda and 4ef5b5e.

📒 Files selected for processing (1)
  • packages/renderless/src/dialog-select/index.ts (4 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: PR E2E Test (pnpm test:e2e3)
🔇 Additional comments (2)
packages/renderless/src/dialog-select/index.ts (2)

64-64:

✅ Verification successful

Verify backward compatibility.

The function signatures have been updated to include new parameters ($table and event). These changes might break existing callers if they're directly invoking these functions.

Make sure all existing callers are updated to match the new parameter structure:

Also applies to: 99-99, 580-580


🏁 Script executed:

#!/bin/bash
# Check for direct invocations of these functions to ensure they're properly updated
echo "Checking for direct invocations of the handler functions..."
rg "\.multiGridSelectAll\(|\.multiGridSelectChange\(|\.multiGridRadioChange\(" --type ts

Length of output: 219


Backward compatibility verified – no direct invocations found

  • Searched for .multiGridSelectAll(, .multiGridSelectChange(, and .multiGridRadioChange( in all TypeScript files; no direct calls were found.
  • Since no existing callers invoke these handlers directly, adding the $table and event parameters does not introduce breaking changes.

578-589:

❓ Verification inconclusive

Verify integration with calling components.

The implementation for multiGridRadioChange follows the same pattern as the other handlers. The event transparency feature is now properly implemented for all three event types.

Make sure that components calling these methods pass the required $table parameter:


🏁 Script executed:

#!/bin/bash
# Search for calls to these handlers to verify they pass the $table parameter
echo "Searching for calls to the modified event handlers..."
rg -A 2 "multiGridSelectAll|multiGridSelectChange|multiGridRadioChange" --type ts

Length of output: 2559


🏁 Script executed:

# Inspect how multiGridRadioChange is registered and used in vue.ts
rg -C10 "multiGridRadioChange" --type ts packages/renderless/src/dialog-select/vue.ts

# Search for where radioChange event is emitted or passed into child components
rg -C10 "radioChange" --type ts packages/renderless/src/dialog-select/vue.ts

Length of output: 2192


Verify $table is passed to multiGridRadioChange callers.

The new handler correctly forwards radioChange({ row, $table }, event) to props.gridOp.events.radioChange, but we didn’t find any usages in the TypeScript files. Please confirm in your Vue templates that every <Grid> (or similar) binding for @radioChange is invoking the handler with both the event payload and the $table reference. For example, run:

rg -R "radioChange" -g "*.vue"

and ensure each occurrence looks something like:

<MyGrid
  :data="items"
  @radioChange="api.multiGridRadioChange($event)"
  ref="tableRef"
/>
<!-- where $event includes row and $table -->

or explicitly passes the component’s table instance:

@radioChange="api.multiGridRadioChange({ row: $event.row, $table: tableRef }, $event)"

@zzcr zzcr merged commit 99ba255 into dev May 8, 2025
9 of 11 checks passed
@zzcr zzcr deleted the add-dialog-select-events-0508 branch May 8, 2025 07:16
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.

1 participant