tests and refactoring for toggle and toggleGroup component

[GoldGroove06]

#750

Summary by CodeRabbit

• New Features

  • Enhanced Toggle component with more flexible styling options
  • Added nextItem and previousItem methods to toggle context
  • Improved type safety for ToggleGroup and ToggleItem components

• Tests

  • Added comprehensive test suite for Toggle and ToggleGroup components
  • Verified rendering, selection handling, and interaction behaviors

• Improvements

  • Refined error handling in toggle navigation
  • Made component props more flexible and optional

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request introduces comprehensive changes to the Toggle and ToggleGroup components, focusing on enhancing type safety, improving component flexibility, and adding robust test coverage. The modifications include updating type declarations, refining context initialization, making props optional, and implementing a comprehensive test suite for both Toggle and ToggleGroup components. The changes aim to improve the components' usability, type safety, and overall reliability.

Changes

File	Change Summary
src/components/ui/Toggle/Toggle.tsx	Enhanced className prop handling and conditional data-disabled attribute
src/components/ui/Toggle/stories/Toggle.stories.js	Minor formatting update with trailing comma
src/components/ui/Toggle/tests/Toggle.test.js	Added comprehensive unit tests for Toggle component
src/components/ui/ToggleGroup/ToggleGroup.tsx	Updated items parameter type declaration
src/components/ui/ToggleGroup/contexts/toggleContext.tsx	Added nextItem and previousItem methods, initialized default context values
src/components/ui/ToggleGroup/fragments/ToggleGroupRoot.tsx	Improved reference handling for nextItem and previousItem functions
src/components/ui/ToggleGroup/fragments/ToggleItem.tsx	Made children, value, and props optional in ToggleItemProps
src/components/ui/ToggleGroup/tests/ToggleGroup.test.js	Added comprehensive test suite for ToggleGroup component

Possibly related issues

• Tests for toggle and toggleGroup #750: This PR directly addresses the issue by adding tests for Toggle and ToggleGroup components, which aligns perfectly with the issue's description.

Possibly related PRs

• Toggle Primitive, Toggle, ToggleGroup Refactor #576: Related changes in Toggle component props and rendering logic
• tests and refactoring for toggle and toggleGroup component #755: Tests and refactoring for the Toggle component, enhancing functionality and reliability
• Util classname 2 #631: Class name management using clsx is relevant to the changes in the Toggle component
• Util classname 3 #632: Improvements in class name handling align with changes made in the Toggle component
• Em tests #740: Emphasis on testing aligns with the objectives of the main PR
• AvatarGroup Tests #707: Focus on testing aligns with the objectives of the main PR
• Refactor Badge and BlockQuote components for consistency + Add Tests #721: Overall focus on improving component functionality and reliability aligns with the objectives of the main PR

Suggested labels

automerge

Suggested reviewers

• kotAPI

Poem

🐰 Toggles dance with newfound grace,
Type-safe and tested, they embrace
Flexibility's sweet refrain,
Components singing their domain!
CodeRabbit's magic, clear and bright ✨

---

📜 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 fd1dd8c and bcd6345.

📒 Files selected for processing (8)

• src/components/ui/Toggle/Toggle.tsx (1 hunks)
• src/components/ui/Toggle/stories/Toggle.stories.js (1 hunks)
• src/components/ui/Toggle/tests/Toggle.test.js (1 hunks)
• src/components/ui/ToggleGroup/ToggleGroup.tsx (1 hunks)
• src/components/ui/ToggleGroup/contexts/toggleContext.tsx (1 hunks)
• src/components/ui/ToggleGroup/fragments/ToggleGroupRoot.tsx (1 hunks)
• src/components/ui/ToggleGroup/fragments/ToggleItem.tsx (1 hunks)
• src/components/ui/ToggleGroup/tests/ToggleGroup.test.js (1 hunks)

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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. (Beta)
• @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.