Migration shards to fragments final batch

[GoldGroove06]

Issue #498 . Migrated the names of shards to fragments with changes in import to respective function.
List of components migrated

• Progress
• Table
• Tabs
• TextArea
• ToggleGroup
• Tree

Summary by CodeRabbit

• Refactor
  • Updated import paths for various components (Progress, Table, Tabs, TextArea, ToggleGroup, Tree) from the "shards" directory to the "fragments" directory, improving component organization without altering functionality.

[coderabbitai]

Walkthrough

This pull request involves updating the import paths for several UI components across multiple files. Specifically, components previously imported from the shards directory have been relocated to the fragments directory. The modifications affect the Progress, Table, Tabs, TextArea, ToggleGroup, and Tree components. No changes were made to the functionality, props, or exported entities of these components; only the import paths were altered to reflect the new directory structure.

Changes

File	Change Summary
src/components/ui/Progress/Progress.tsx	Updated import paths for ProgressRoot and ProgressIndicator from shards to fragments.
src/components/ui/Table/Table.tsx	Updated import paths for TableRoot, TableHead, TableBody, TableRow, TableColumnCellHeader, and TableCell from shards to fragments.
src/components/ui/Tabs/Tabs.tsx	Updated import paths for TabList, TabContent, and TabRoot from shards to fragments.
src/components/ui/TextArea/TextArea.tsx	Updated import paths for TextAreaRoot and TextAreaInput from shards to fragments.
src/components/ui/ToggleGroup/ToggleGroup.tsx	Updated import paths for ToggleGroupRoot and ToggleItem from shards to fragments.
src/components/ui/Tree/Tree.tsx	Updated import paths for TreeRoot and TreeItem from shards to fragments.

Possibly related PRs

• Release/0.0.22 #391: The changes in this PR include updates to the package.json file that introduce new component paths, including TextArea, which is relevant to the main PR's changes in import paths for TextAreaRoot and TextAreaInput.
• Tree Component #490: This PR introduces a new Tree component, which includes changes to the TreeRoot component. While the main PR does not directly modify the Tree component, both involve similar restructuring of component organization from "shards" to "fragments".

Suggested reviewers

• kotAPI
• impirios

🐰 In the land of code, where paths do roam,
We’ve moved our imports to a new home.
From shards to fragments, they now reside,
Keeping our components organized with pride.
Hopping along, our functions stay bright,
With paths all updated, everything’s right! 🥕

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between f6c960b and e5c85ec.

📒 Files selected for processing (6)

• src/components/ui/Progress/Progress.tsx (1 hunks)
• src/components/ui/Table/Table.tsx (1 hunks)
• src/components/ui/Tabs/Tabs.tsx (1 hunks)
• src/components/ui/TextArea/TextArea.tsx (1 hunks)
• src/components/ui/ToggleGroup/ToggleGroup.tsx (1 hunks)
• src/components/ui/Tree/Tree.tsx (1 hunks)

✅ Files skipped from review due to trivial changes (6)

• src/components/ui/Progress/Progress.tsx
• src/components/ui/Table/Table.tsx
• src/components/ui/Tabs/Tabs.tsx
• src/components/ui/TextArea/TextArea.tsx
• src/components/ui/ToggleGroup/ToggleGroup.tsx
• src/components/ui/Tree/Tree.tsx

---

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