Skip to content
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

allow passing title to ButtonView when disabled #5073

Merged
merged 1 commit into from
Nov 8, 2024

Conversation

manivoxel51
Copy link
Contributor

@manivoxel51 manivoxel51 commented Nov 7, 2024

What changes are proposed in this pull request?

  • realized there is a TitleProvider with a title property but it was only rendering when not disabled. if we allow it to have a title regardless of disabled or not, we can pass teams specific title for permissioning
Screen.Recording.2024-11-07.at.3.47.20.PM.mov

How is this patch tested? If it is not, please explain why.

(Details)

Release Notes

Is this a user-facing change that should be mentioned in the release notes?

  • No. You can skip the rest of this section.
  • Yes. Give a description of this change to be included in the release
    notes for FiftyOne users.

(Details in 1-2 sentences. You can just refer to another PR with a description
if this PR is part of a larger change.)

What areas of FiftyOne does this PR affect?

  • App: FiftyOne application changes
  • Build: Build and test infrastructure changes
  • Core: Core fiftyone Python library changes
  • Documentation: FiftyOne documentation changes
  • Other

Summary by CodeRabbit

  • New Features

    • Introduced an optional title property for button views in modals, enhancing configuration flexibility.
    • Improved tooltip behavior to consistently display titles regardless of button state.
  • Bug Fixes

    • Adjusted button click behavior to ensure actions are only triggered when appropriate, enhancing user interaction.

Copy link
Contributor

coderabbitai bot commented Nov 7, 2024

Walkthrough

The changes introduced in this pull request enhance the modal and button view components by adding a new optional title property to the ModalButtonView interface and modifying the tooltip behavior in the ButtonView component. The ModalBase now conditionally disables the primary button based on the presence of tags when the functionality is set to "tagging." These modifications aim to improve the flexibility of button configurations and refine user interaction through better control over button states.

Changes

File Path Change Summary
app/packages/components/src/components/ModalBase/ModalBase.tsx Added optional title property to ModalButtonView interface; modified useEffect to conditionally disable the primary button based on tags.
app/packages/core/src/plugins/SchemaIO/components/ButtonView.tsx Updated tooltip handling to always pass title prop; adjusted onClick handler to clarify control flow.

Possibly related PRs

Suggested labels

feature, app

Suggested reviewers

  • lanzhenw
  • imanjra
  • Br2850

🐇 In the modal, a title we now see,
For buttons that click with glee!
Tags will enable, or so they say,
Making user choices bright as day.
With tooltips clear, the clicks align,
A hop, a skip, all works just fine! 🌟


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?

❤️ 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 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.

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.

Copy link
Contributor

@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

🧹 Outside diff range and nitpick comments (3)
app/packages/core/src/plugins/SchemaIO/components/ButtonView.tsx (1)

41-41: LGTM! Consider adding prop validation.

The direct passing of the title prop aligns with the PR objective to show tooltips for disabled buttons. However, consider adding proper TypeScript validation:

+ interface ButtonViewProps extends ViewPropsType {
+   schema: {
+     view?: {
+       title?: string;
+       // ... other existing view props
+     };
+   };
+ }

- export default function ButtonView(props: ViewPropsType) {
+ export default function ButtonView(props: ButtonViewProps) {
app/packages/components/src/components/ModalBase/ModalBase.tsx (2)

108-108: Consider adding documentation and validation for the title property

While the implementation correctly enables passing titles to ButtonView, consider these improvements:

  1. Add JSDoc comments explaining the purpose of the title property
  2. Add validation to ensure the title is a non-empty string when provided

Example implementation:

+ // Title to be displayed in the button tooltip, shown even when button is disabled
  title: props?.title,
+ // Validate title if provided
+ ...(props?.title && typeof props.title !== 'string' && {
+   title: String(props.title)
+ }),

Line range hint 171-184: Fix useEffect dependency array to prevent stale closures

The effect uses primaryButtonView object but only lists primaryButtonView.params in its dependency array. This could lead to stale closures if other properties of primaryButtonView change.

Update the dependency array to include all used values:

  useEffect(() => {
    if (
      (functionality === "tagging" || functionality === "Tagging") &&
      (!primaryButtonView.params ||
        !primaryButtonView.params.tags ||
        primaryButtonView.params.tags.length === 0)
    ) {
      setPrimaryButtonView({
        ...primaryButtonView,
        disabled: true,
      });
    } else {
      setPrimaryButtonView({
        ...primaryButtonView,
        disabled: false,
      });
    }
-  }, [primaryButtonView.params]);
+  }, [primaryButtonView, functionality]);
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between b06590c and b6c008f.

📒 Files selected for processing (2)
  • app/packages/components/src/components/ModalBase/ModalBase.tsx (2 hunks)
  • app/packages/core/src/plugins/SchemaIO/components/ButtonView.tsx (1 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
app/packages/components/src/components/ModalBase/ModalBase.tsx (1)

Pattern **/*.{ts,tsx}: Review the Typescript and React code for conformity with best practices in React, Recoil, Graphql, and Typescript. Highlight any deviations.

app/packages/core/src/plugins/SchemaIO/components/ButtonView.tsx (1)

Pattern **/*.{ts,tsx}: Review the Typescript and React code for conformity with best practices in React, Recoil, Graphql, and Typescript. Highlight any deviations.

🔇 Additional comments (2)
app/packages/core/src/plugins/SchemaIO/components/ButtonView.tsx (1)

Line range hint 41-63: Add test coverage for tooltip behavior.

Please ensure test coverage for:

  • Tooltip visibility when button is disabled
  • Correct title rendering in both enabled/disabled states
app/packages/components/src/components/ModalBase/ModalBase.tsx (1)

52-52: LGTM: Interface change follows TypeScript best practices

The addition of the optional title property to the ModalButtonView interface is well-structured and properly typed.

@manivoxel51 manivoxel51 merged commit e55664f into release/v1.1.0 Nov 8, 2024
10 of 11 checks passed
@manivoxel51 manivoxel51 deleted the feat/add-tooltip-btn branch November 8, 2024 04:45
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.

2 participants