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

feat: Introduce <ToggleIconButton/> for single toggles and replace <ToggleButtonGroup/>. #191

Merged
merged 9 commits into from
Feb 26, 2025

Conversation

Henry8192
Copy link
Collaborator

@Henry8192 Henry8192 commented Feb 24, 2025

Description

ToggleButtonGroup is causing inconvenience whenever isCaseSensitive or isRegex updates. It is only used because the button pressed status needs to be shown visually. The current implementation achieves the same goal without using ToggleButtonGroup, and are easier for query options to update.

Checklist

  • The PR satisfies the contribution guidelines.
  • This is a breaking change and that has been indicated in the PR title, OR this isn't a
    breaking change.
  • Necessary docs have been updated, OR no docs need to be updated.

Validation performed

Search Scheduling without any query options, search results are found and shown;
Enable case sensitive, no search results are found.

example.zip

Summary by CodeRabbit

  • New Features

    • Introduced a new ToggleIconButton component for enhanced user interaction with search options.
    • Added interactive toggle buttons for enabling case sensitivity and regex search options, offering immediate visual feedback.
  • Refactor

    • Simplified the search panel functionality by streamlining option handling and state management.
  • Style

    • Improved layout consistency with refined button dimensions for a more polished user interface.

Copy link

coderabbitai bot commented Feb 24, 2025

Walkthrough

This update modifies both the styling and state management within the SearchTabPanel component. In the CSS file, explicit dimensions are applied to the .query-option-button class using !important. In the TypeScript file, the previous enum-based approach and its utility functions have been removed, and two new state variables along with dedicated toggle handlers have been introduced to manage the case sensitivity and regex options. Additionally, the UI layout has been adjusted to replace the ToggleButtonGroup with a Stack containing a new ToggleIconButton component.

Changes

Files Summary of Changes
src/…/SearchTabPanel/index.css Updated .query-option-button class with explicit width (1.5rem), height (1.5rem), min-width (0), and min-height (0), all marked as !important to enforce strict sizing.
src/…/SearchTabPanel/index.tsx Removed the QUERY_OPTION enum and associated utility functions; added state variables (isCaseSensitive, isRegex) and new toggle handler functions (handleCaseSensitivityButtonClick, handleRegexButtonClick); replaced the ToggleButtonGroup with a Stack containing the new ToggleIconButton component and updated query submission logic.
src/…/SearchTabPanel/ToggleIconButton.tsx Introduced ToggleIconButton component that extends IconButton, adding visual feedback for pressed state and tooltip support.

Possibly related PRs

Suggested reviewers

  • junhaoliao
✨ Finishing Touches
  • 📝 Generate Docstrings

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 generate docstrings to generate docstrings for 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.

@Henry8192 Henry8192 changed the title feat(SearchTabPanel): Toggle button group removal feat(SearchTabPanel): Replace ToggleButtonGroup with Stack for query option icon buttons Feb 24, 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: 0

🧹 Nitpick comments (1)
src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx (1)

68-82: Consider optimizing the button handlers.

The handlers follow a consistent pattern but could be optimized to avoid redundant state updates.

Consider this optimization:

-    const handleCaseButtonPressed = () => {
-        handleQuerySubmit({
-            isCaseSensitive: !isCaseSensitive,
-            isRegex: isRegex,
-        });
-        setIsCaseSensitive(!isCaseSensitive);
-    };
+    const handleCaseButtonPressed = () => {
+        const newIsCaseSensitive = !isCaseSensitive;
+        setIsCaseSensitive(newIsCaseSensitive);
+        handleQuerySubmit({
+            isCaseSensitive: newIsCaseSensitive,
+            isRegex: isRegex,
+        });
+    };

-    const handleRegexButtonPressed = () => {
-        handleQuerySubmit({
-            isCaseSensitive: isCaseSensitive,
-            isRegex: !isRegex,
-        });
-        setIsRegex(!isRegex);
-    };
+    const handleRegexButtonPressed = () => {
+        const newIsRegex = !isRegex;
+        setIsRegex(newIsRegex);
+        handleQuerySubmit({
+            isCaseSensitive: isCaseSensitive,
+            isRegex: newIsRegex,
+        });
+    };
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ec35a06 and 0fb58ff.

📒 Files selected for processing (2)
  • src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.css (1 hunks)
  • src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx (5 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
`**/*.{cpp,hpp,java,js,jsx,tpp,ts,tsx}`: - Prefer `false == ...

**/*.{cpp,hpp,java,js,jsx,tpp,ts,tsx}: - Prefer false == <expression> rather than !<expression>.

  • src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx
🧠 Learnings (1)
src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.css (1)
Learnt from: junhaoliao
PR: y-scope/yscope-log-viewer#107
File: src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.css:14-18
Timestamp: 2024-11-14T04:35:00.986Z
Learning: In `src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.css`, the use of `!important` flags is necessary for overriding styles in the `.query-input-box` class.
🔇 Additional comments (5)
src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.css (1)

20-24: LGTM! The button dimensions are appropriate.

The explicit dimensions with !important flags are necessary and appropriate for icon buttons. Setting both fixed and minimum dimensions ensures consistent button sizing.

src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx (4)

11-11: LGTM! The Stack import is appropriate.

The Stack component is a suitable replacement for ToggleButtonGroup to manage button layout.


47-48: LGTM! The state management is simplified.

Using boolean flags for case sensitivity and regex options is more straightforward than the previous enum-based approach.


56-58: LGTM! The query submission is simplified.

Direct use of boolean flags makes the code more readable and maintainable by removing the need for utility functions.


111-148: LGTM! The UI changes are well-implemented.

The Stack component with IconButtons provides a clean and accessible replacement for the toggle button group. The buttons are properly configured with tooltips, aria attributes, and consistent styling.

@Henry8192 Henry8192 requested a review from junhaoliao February 24, 2025 21:24
Copy link
Member

@junhaoliao junhaoliao left a comment

Choose a reason for hiding this comment

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

can we create a custom component in src/components for the toggle buttons? e.g.,

interface ToggleIconButton extends IconButton {
    isActive: boolean;
}

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: 2

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 0fb58ff and 440ac6a.

📒 Files selected for processing (2)
  • src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/ToggleIconButton.tsx (1 hunks)
  • src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx (5 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
`**/*.{cpp,hpp,java,js,jsx,tpp,ts,tsx}`: - Prefer `false == ...

**/*.{cpp,hpp,java,js,jsx,tpp,ts,tsx}: - Prefer false == <expression> rather than !<expression>.

  • src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/ToggleIconButton.tsx
  • src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx
🔇 Additional comments (3)
src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/ToggleIconButton.tsx (1)

1-44: Well-implemented component with good accessibility practices!

This new ToggleIconButton component is a well-structured solution that provides the toggle functionality needed for the query options. I especially appreciate:

  • The clear TypeScript interface extending the base IconButtonProps
  • The use of aria-pressed attribute for accessibility
  • The thorough JSDoc documentation
  • The component composition with Tooltip for better UX

This implementation aligns well with the PR objective of simplifying the query option state management.

src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx (2)

45-46: Great simplification of state management

The replacement of the enum-based approach with direct boolean state variables is a good improvement. This makes the code more maintainable and easier to understand.

The state variables have clear, descriptive names, and they're used consistently throughout the component.

Also applies to: 54-56


109-132: Good UI structure with Stack and ToggleIconButton

The replacement of ToggleButtonGroup with Stack and custom ToggleIconButton components creates a cleaner implementation that more directly manages the toggle states.

The props passed to ToggleIconButton are well-structured and include all necessary information including accessibility attributes and tooltips.

@junhaoliao
Copy link
Member

For the PR title, how about:

feat: Introduce `<ToggleIconButton/>` for single toggles and replace `<ToggleButtonGroup/>`.

@Henry8192 Henry8192 changed the title feat(SearchTabPanel): Replace ToggleButtonGroup with Stack for query option icon buttons feat: Introduce <ToggleIconButton/> for single toggles and replace <ToggleButtonGroup/>. Feb 25, 2025
@Henry8192 Henry8192 requested a review from junhaoliao February 26, 2025 18:13
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

♻️ Duplicate comments (2)
src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx (2)

67-72: ⚠️ Potential issue

Race condition in case sensitivity toggle handler.

The function submits the query using the current state value and then updates the state. This creates a race condition where the query might not use the toggled value.

Apply this fix:

const handleCaseSensitivityButtonClick = () => {
+    const newCaseSensitiveValue = !isCaseSensitive;
+    setIsCaseSensitive(newCaseSensitiveValue);
    handleQuerySubmit({
-        isCaseSensitive: isCaseSensitive,
+        isCaseSensitive: newCaseSensitiveValue,
    });
-    setIsCaseSensitive(!isCaseSensitive);
};

74-79: ⚠️ Potential issue

Race condition in regex toggle handler.

Similar to the case sensitivity handler, this function has a race condition where the query is submitted before the state is updated.

Apply this fix:

const handleRegexButtonClick = () => {
+    const newRegexValue = !isRegex;
+    setIsRegex(newRegexValue);
    handleQuerySubmit({
-        isRegex: !isRegex,
+        isRegex: newRegexValue,
    });
-    setIsRegex(!isRegex);
};
🧹 Nitpick comments (2)
src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx (2)

69-70: Redundant property in query submission.

Setting isCaseSensitive: isCaseSensitive is redundant as this value is already set in the base query args at line 55.

Remove the unnecessary property:

const handleCaseSensitivityButtonClick = () => {
-    handleQuerySubmit({
-        isCaseSensitive: isCaseSensitive,
-    });
+    handleQuerySubmit({});
    setIsCaseSensitive(!isCaseSensitive);
};

76-76: Coding guideline: Use of negation operator.

According to the coding guidelines provided, we should prefer false == <expression> rather than !<expression>.

handleQuerySubmit({
-    isRegex: !isRegex,
+    isRegex: false == isRegex,
});

Note: There was a previous discussion in comments where the team decided to keep using ! for readability in this specific case. If that decision still stands, you can ignore this comment.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 4bade57 and 9471de0.

📒 Files selected for processing (1)
  • src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx (4 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
`**/*.{cpp,hpp,java,js,jsx,tpp,ts,tsx}`: - Prefer `false == ...

**/*.{cpp,hpp,java,js,jsx,tpp,ts,tsx}: - Prefer false == <expression> rather than !<expression>.

  • src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx
🔇 Additional comments (4)
src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx (4)

10-10: LGTM: Import changes for new component structure.

The addition of Stack from MUI Joy and the new ToggleIconButton component follows the PR's objective to replace the previous ToggleButtonGroup implementation.

Also applies to: 31-31


46-47: LGTM: State variables for direct query option management.

The implementation of dedicated state variables for case sensitivity and regex options improves clarity compared to the previous enum-based approach.


55-56: LGTM: Updated query submission with new state variables.

The query submission handler correctly uses the new state variables and the spread operator to override with any new values.

Also applies to: 58-58


108-135: LGTM: Improved UI with dedicated toggle buttons.

The new UI implementation with Stack and ToggleIconButton components provides a cleaner and more maintainable solution than the previous implementation. Each toggle button now has clear tooltips and visual feedback.

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

♻️ Duplicate comments (2)
src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx (2)

67-72: ⚠️ Potential issue

Fix potential race condition and follow coding guidelines

The toggle handler has two issues:

  1. It submits the query before updating the state, which could lead to a race condition where the query uses the old state value.
  2. The negation operator (!isCaseSensitive) doesn't follow the coding guideline that prefers false == <expression> over !<expression>.

Apply this fix:

const handleCaseSensitivityButtonClick = () => {
+    const newCaseSensitiveValue = false == isCaseSensitive;
+    setIsCaseSensitive(newCaseSensitiveValue);
    handleQuerySubmit({
-        isCaseSensitive: !isCaseSensitive,
+        isCaseSensitive: newCaseSensitiveValue,
    });
-    setIsCaseSensitive(!isCaseSensitive);
};

74-79: ⚠️ Potential issue

Fix potential race condition and follow coding guidelines

The regex toggle handler has the same issues as the case sensitivity handler:

  1. It submits the query before updating the state, which could lead to a race condition.
  2. The negation operator (!isRegex) doesn't follow the coding guideline that prefers false == <expression> over !<expression>.

Apply this fix:

const handleRegexButtonClick = () => {
+    const newRegexValue = false == isRegex;
+    setIsRegex(newRegexValue);
    handleQuerySubmit({
-        isRegex: !isRegex,
+        isRegex: newRegexValue,
    });
-    setIsRegex(!isRegex);
};
🧹 Nitpick comments (1)
src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx (1)

41-41: Consider refactoring to reduce function size

The ESLint disable comment indicates the function exceeds the line limit. Consider if some logic could be extracted into separate helper functions to improve readability and maintainability.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 9471de0 and 59ebbc6.

📒 Files selected for processing (2)
  • src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/ToggleIconButton.tsx (1 hunks)
  • src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx (4 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/ToggleIconButton.tsx
🧰 Additional context used
📓 Path-based instructions (1)
`**/*.{cpp,hpp,java,js,jsx,tpp,ts,tsx}`: - Prefer `false == ...

**/*.{cpp,hpp,java,js,jsx,tpp,ts,tsx}: - Prefer false == <expression> rather than !<expression>.

  • src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx
🔇 Additional comments (2)
src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx (2)

108-135: UI update looks good

The replacement of ToggleButtonGroup with a Stack containing ToggleIconButton components is well implemented. Each button properly passes the isChecked state and has appropriate tooltip titles.


46-47: Good state initialization

The new state variables are correctly initialized to false as default values.

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)
src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx (2)

66-69: Consider updating state before submitting to prevent potential race conditions

The current implementation submits the query before updating the state. This could potentially lead to race conditions where the state update isn't completed before the next render cycle.

Consider reversing the order of operations:

const handleCaseSensitivityButtonClick = () => {
+    setIsCaseSensitive(!isCaseSensitive);
     handleQuerySubmit({isCaseSensitive: !isCaseSensitive});
-    setIsCaseSensitive(!isCaseSensitive);
};

71-74: Consider updating state before submitting to prevent potential race conditions

Similar to the case sensitivity handler, this function submits the query before updating the state, which could lead to potential race conditions.

Consider reversing the order of operations:

const handleRegexButtonClick = () => {
+    setIsRegex(!isRegex);
     handleQuerySubmit({isRegex: !isRegex});
-    setIsRegex(!isRegex);
};
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 59ebbc6 and 4756dfa.

📒 Files selected for processing (1)
  • src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx (5 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
`**/*.{cpp,hpp,java,js,jsx,tpp,ts,tsx}`: - Prefer `false == ...

**/*.{cpp,hpp,java,js,jsx,tpp,ts,tsx}: - Prefer false == <expression> rather than !<expression>.

  • src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx
🔇 Additional comments (5)
src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx (5)

67-67: Consider using false == expression pattern per coding guidelines

The negation operator usage (!isCaseSensitive) doesn't follow the coding guideline that suggests using false == <expression> instead of !<expression>.

Note: I see from past comments that the team had a discussion about this and decided to use ! for better readability in this particular case. If that decision still holds, this can be ignored.


72-72: Consider using false == expression pattern per coding guidelines

The negation operator usage (!isRegex) doesn't follow the coding guideline that suggests using false == <expression> instead of !<expression>.

Note: Based on past comments, the team had discussed this and decided to use ! for better readability in this context. If that decision still holds, this can be ignored.


103-130: Great UI improvement with the new ToggleIconButton component

The replacement of the previous toggle button implementation with the new ToggleIconButton component creates a cleaner UI and better separation of concerns. The Stack layout also provides a more consistent spacing solution.


45-46: Good state management update

Moving to direct state variables for isCaseSensitive and isRegex simplifies the code and makes state management more straightforward than the previous enum-based approach.


54-56: Solid update to the query submission logic

The updated query submission function properly utilizes the new state variables, making the code more maintainable and reducing complexity.

@Henry8192 Henry8192 merged commit 8ddd27a into y-scope:main Feb 26, 2025
3 checks passed
@Henry8192 Henry8192 deleted the ToggleButtonGroup-removal branch February 26, 2025 19:42
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