Skip to content

Tshepo/en/filter #3377

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

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

Tshepo1103-lab
Copy link
Contributor

@Tshepo1103-lab Tshepo1103-lab commented Jun 10, 2025

#3240

Summary by CodeRabbit

  • New Features

    • Added tooltip support to the advanced filter button for improved user guidance.
  • Improvements

    • The width setting for the advanced filter button is now always visible, regardless of button type.
    • Updated the permissions input in the security settings to use a more streamlined and consistent component.
  • Style

    • Minor adjustments to style handling for better maintainability.

Copy link
Contributor

coderabbitai bot commented Jun 10, 2025

Walkthrough

The changes update the AdvancedFilterButton component and its related files by enhancing the button with a tooltip, simplifying style handling, refactoring import statements, and modifying settings configuration. The permission input in the settings form is generalized, and the style hook's parameter is streamlined for clarity and consistency.

Changes

File(s) Change Summary
.../advancedFilterButton/advancedFilterButton.tsx Wrapped Button in Tooltip, added Tooltip import, simplified useStyles parameter.
.../advancedFilterButton/advancedFilterButtonComponent.tsx Cleaned imports, simplified rendering, updated migration version numbers.
.../advancedFilterButton/settingsForm.ts Removed conditional hiding of width input, replaced permission autocomplete with generic permissions input.
.../advancedFilterButton/style.ts Changed useStyles parameter from object destructure to direct fontSize, minor style indentation adjustment.

Poem

A button now glows with a tip on display,
Permissions more flexible, in a brand-new way.
Styles flow simply, no objects in sight,
Imports are tidy, the code feels light.
With every small tweak, our table feels bright!

((\
( -.-)
o_(")(")


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between fc45403 and 9c9ef61.

📒 Files selected for processing (4)
  • shesha-reactjs/src/designer-components/dataTable/advancedFilterButton/advancedFilterButton.tsx (3 hunks)
  • shesha-reactjs/src/designer-components/dataTable/advancedFilterButton/advancedFilterButtonComponent.tsx (3 hunks)
  • shesha-reactjs/src/designer-components/dataTable/advancedFilterButton/settingsForm.ts (1 hunks)
  • shesha-reactjs/src/designer-components/dataTable/advancedFilterButton/style.ts (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: build-attempt
🔇 Additional comments (9)
shesha-reactjs/src/designer-components/dataTable/advancedFilterButton/advancedFilterButton.tsx (3)

2-2: LGTM! Tooltip import added correctly.

The Tooltip import from 'antd' is properly added to support the new tooltip functionality.


19-19: LGTM! useStyles call simplified correctly.

The change from passing an object {fontSize: props.styles?.fontSize} to directly passing props.styles?.fontSize aligns with the updated function signature in style.ts. This simplification improves readability.


72-90: LGTM! Tooltip implementation is correct.

The Button component is properly wrapped with the Tooltip component, and the tooltip text is correctly sourced from props.tooltip. This enhances user experience by providing contextual help.

shesha-reactjs/src/designer-components/dataTable/advancedFilterButton/style.ts (2)

3-3: LGTM! Function signature simplification improves API design.

Changing from destructured object parameter {fontSize} to direct parameter fontSize: string | number simplifies the API and makes the function more straightforward to use. The type annotation is appropriate.


37-37: LGTM! CSS formatting maintained.

The indentation adjustment maintains code consistency without affecting functionality.

shesha-reactjs/src/designer-components/dataTable/advancedFilterButton/advancedFilterButtonComponent.tsx (3)

1-9: LGTM! Import cleanup improves maintainability.

The import statements have been properly reorganized and unused imports (QuestionCircleOutlined, Show, Tooltip) have been removed. This reduces bundle size and improves code clarity.


17-20: LGTM! Factory rendering simplified appropriately.

The removal of the wrapping <div> and conditional tooltip logic is correct since the tooltip functionality has been moved into the AdvancedFilterButton component itself. This simplifies the component structure.


32-33:

❓ Verification inconclusive

Verify the migration version number changes.

The migration version numbers were changed from 3 and 4 to 1 and 2. Ensure this change is intentional and doesn't break existing migration paths.


🏁 Script executed:

#!/bin/bash
# Description: Check for other migration references to understand the versioning strategy
# Expected: Find other migration configurations to understand the versioning pattern

echo "Searching for migration version patterns in the codebase..."
rg -A 3 -B 3 "\.add<.*>\([0-9]+," --type ts

Length of output: 323


🏁 Script executed:

#!/bin/bash
# Description: Search for all .add<…>(version,…) calls across TS and TSX files
echo "Scanning for migration steps in .ts and .tsx files…"
rg "\.add<[^>]+>\([0-9]+," -n -g "*.ts" -g "*.tsx"

Length of output: 314


Verify Migration Version Numbers

I searched the entire codebase for other .add<…>(version, …) calls but didn’t find any additional migration steps. Please confirm that resetting these steps to versions 1 and 2 here is intentional and won’t conflict with any existing migration history.

• Location: shesha-reactjs/src/designer-components/dataTable/advancedFilterButton/advancedFilterButtonComponent.tsx lines 32–33

shesha-reactjs/src/designer-components/dataTable/advancedFilterButton/settingsForm.ts (1)

662-669: LGTM! Permission input standardized.

The change from addPermissionAutocomplete to addSettingsInput with inputType: 'permissions' appears to be a standardization effort. This approach provides consistency with other form inputs while maintaining the same functionality.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant