rad-ui/ui

AI Summary: This issue proposes refactoring four `DataList` sub-components (DataListItem, DataListLabel, DataListRoot, DataListValue) to incorporate React's `forwardRef` functionality. The goal is to enable proper ref forwarding for these specific components.

AI Summary: This issue is to refactor the 'Heading' component to properly forward its ref using React's `forwardRef` API. It's identified as a suitable task for new contributors.

AI Summary: This issue proposes refactoring the `Skeleton` component to utilize `forwardRef`. This change is intended to allow the component to properly forward refs to its underlying DOM element or component.

AI Summary: This issue requires refactoring the `TreeItem` and `TreeRoot` components to properly implement `React.forwardRef`. The goal is to enable these components to correctly receive and forward refs, likely to their underlying DOM elements or child components. This task is explicitly labeled as a good first issue.

AI Summary: This issue proposes refactoring the `TooltipRoot` component to utilize `React.forwardRef`. The goal is to enable the component to correctly pass a ref to its underlying element, improving its integration and accessibility. It is labeled as a good first issue, indicating low complexity.

AI Summary: This issue proposes refactoring the `ToggleGroupRoot` and `ToggleItem` components to incorporate `forwardRef`. The goal is to enable these components to properly forward refs to their underlying DOM elements or components, and it's labeled as a good task for new contributors.

AI Summary: This issue requests refactoring the `Toggle` component to properly forward its ref using React's `forwardRef` API. It's marked as a good first issue, indicating a straightforward task.

AI Summary: This issue proposes refactoring the 'Theme' component to properly utilize `forwardRef`. The goal is to ensure that refs can be passed through the component as needed. It is marked as a good first issue, indicating a straightforward task.

AI Summary: This issue requests refactoring the `TextAreaInput` and `TextAreaRoot` components to properly forward refs using React's `forwardRef` API. This is a standard practice for allowing parent components to access the underlying DOM element of a child component.

AI Summary: This issue proposes refactoring the `Text` component to utilize `forwardRef`. The goal is to update the component's implementation to correctly pass and handle refs.

AI Summary: This issue proposes refactoring the `Tabs` component and its sub-components (`TabContent`, `TabList`, `TabRoot`, `TabTrigger`) to properly utilize `forwardRef`. This refactoring is aimed at allowing parent components to pass refs down to these specific tab-related components.

AI Summary: This issue proposes refactoring several core table components, including TableBody, TableCell, TableHead, TableRoot, and TableRow, to utilize React's `forwardRef` functionality. The goal is to enable these components to correctly forward refs to their underlying DOM elements or child components.

AI Summary: This issue proposes refactoring the `TabNavLink` and `TabNavRoot` components within the `TabNav` system to utilize `React.forwardRef`. This change will enable parent components to receive a ref to the underlying DOM node of these components.

AI Summary: This issue proposes refactoring one or more components, likely named 'Strong' or within a 'Strong' category, to correctly utilize `forwardRef`. It's identified as a suitable task for new contributors.

AI Summary: This issue proposes refactoring the `SwitchRoot` and `SwitchThumb` components to utilize React's `forwardRef` API. This change is necessary to allow refs to be passed down to the underlying DOM elements or child components.

AI Summary: This issue is about refactoring three specific components: SplitterHandle, SplitterPanel, and SplitterRoot. The refactoring task involves implementing React's `forwardRef` functionality for each of these components, likely to enable proper ref passing from parent components.

AI Summary: This issue proposes refactoring several sub-components of a Slider component, specifically SliderRange, SliderRoot, SliderThumb, and SliderTrack, to utilize React's `forwardRef` API. This change will enable parent components to pass refs down to these child components.

AI Summary: This issue proposes refactoring the 'Separator' component to utilize React's `forwardRef` functionality. The goal is to ensure the component correctly exposes a ref to its underlying DOM element or component.

AI Summary: This issue involves refactoring several `Select` sub-components, including `SelectContent`, `SelectGroup`, and `SelectTrigger`, to properly utilize `forwardRef`. The goal is to ensure these components correctly forward refs to their underlying DOM elements or components.

AI Summary: This issue proposes refactoring several sub-components of the `ScrollArea` component (Corner, Root, Scrollbar, Thumb, Viewport) to utilize React's `forwardRef` API. This is a standard practice for allowing parent components to pass refs down to their children.

AI Summary: This issue proposes refactoring the `RadioGroup` component and its sub-components (`RadioGroupIndicator`, `RadioGroupItem`, `RadioGroupLabel`, `RadioGroupRoot`) to utilize `forwardRef`. The goal is to enable proper ref forwarding through these components.

AI Summary: This issue proposes refactoring the `RadioCardsItem` and `RadioCardsRoot` components to utilize `forwardRef`. The goal is to enable these components to properly forward refs to their underlying DOM elements or child components.

AI Summary: This issue proposes refactoring the `Radio` component to utilize `forwardRef`. This change will enable the component to correctly pass a ref down to its underlying DOM element or another component, improving its accessibility and integration with other React features.

AI Summary: This GitHub issue proposes refactoring the 'Quote' component to utilize React's `forwardRef` functionality. The goal is to enable the component to properly receive and forward refs, improving its reusability and integration with parent components. It is labeled as a 'good first issue', indicating a relatively straightforward task.

AI Summary: This issue outlines the task of refactoring the `ProgressIndicator` and `ProgressRoot` components. The objective is to update these components to correctly use `forwardRef`, enabling them to receive and forward refs from parent components.

AI Summary: This issue involves refactoring the `NumberField` component and its sub-components (`NumberFieldDecrement`, `NumberFieldIncrement`, `NumberFieldInput`, `NumberFieldRoot`) to properly utilize `forwardRef`. This change is necessary to allow refs to be passed through these components.

AI Summary: This issue requires refactoring several `NavigationMenu` components, including `NavigationMenuContent`, `NavigationMenuItem`, `NavigationMenuLink`, `NavigationMenuRoot`, and `NavigationMenuTrigger`, to properly utilize React's `forwardRef` API. The goal is to ensure these components correctly pass refs down to their underlying DOM elements or components.

AI Summary: This issue proposes refactoring multiple Menubar components, including MenubarContent, MenubarItem, and MenubarRoot, to utilize `forwardRef`. The objective is to enable parent components to pass refs down to these Menubar components, enhancing their flexibility and allowing direct access to their underlying DOM elements. This is a standard React refactoring task.

AI Summary: This issue requests refactoring the `Link` component to utilize `React.forwardRef`. This change is necessary to allow refs to be passed down to the underlying DOM element or another component within `Link`.

AI Summary: This issue proposes refactoring the `Kbd` component to correctly use `forwardRef`. The goal is to enable parent components to receive a ref to the underlying DOM element of the `Kbd` component.

AI Summary: This issue proposes refactoring several `HoverCard` sub-components, including `HoverCardArrow`, `HoverCardContent`, `HoverCardPortal`, `HoverCardRoot`, and `HoverCardTrigger`, to utilize React's `forwardRef` API. The goal is to ensure these components correctly forward their refs to underlying DOM elements, which is a standard practice for UI libraries.

AI Summary: This issue proposes refactoring the `Em` component to correctly utilize `forwardRef`. This is necessary for allowing parent components to pass refs down to the underlying DOM element or another component within `Em`.

AI Summary: This issue proposes refactoring a set of `DropdownMenu` related components, including `DropdownMenuContent`, `DropdownMenuItem`, and `DropdownMenuTrigger`, to utilize `forwardRef`. The goal is to enable proper ref forwarding for these components, and it is labeled as a good first issue.

AI Summary: This issue involves refactoring four specific 'Disclosure' components (DisclosureContent, DisclosureItem, DisclosureRoot, DisclosureTrigger) to correctly utilize React's `forwardRef` API. The goal is to ensure these components can properly pass refs down to their underlying elements.

AI Summary: This issue proposes refactoring multiple `Dialog` components, including `DialogClose`, `DialogContent`, and `DialogRoot`, to properly utilize `forwardRef`. The goal is to ensure these components correctly forward their refs.

AI Summary: This issue proposes refactoring several `ContextMenu` components (including Root, Content, Item, Trigger, Portal, Sub, and SubTrigger) to utilize React's `forwardRef` API. The goal is to enable proper ref forwarding for these components.

AI Summary: This issue involves refactoring three specific Collapsible components: `CollapsibleContent`, `CollapsibleRoot`, and `CollapsibleTrigger`. The task is to update these components to properly utilize `forwardRef`. It is labeled as a 'good first issue', indicating it should be relatively straightforward for new contributors.

AI Summary: This issue proposes refactoring existing components to properly utilize `forwardRef`. The task specifically targets components identified as 'Code' that require this refactoring to correctly forward refs. It is labeled as a good first issue, indicating a straightforward implementation.

AI Summary: This issue proposes refactoring several components within the CheckboxGroup, specifically CheckboxGroupIndicator, CheckboxGroupLabel, CheckboxGroupRoot, and CheckboxGroupTrigger, to utilize React's `forwardRef` functionality. The goal is to allow these components to correctly receive and forward refs. It is marked as a good first issue.

AI Summary: This issue proposes refactoring the `CheckboxCards` component family, specifically `CheckboxCardsContent`, `CheckboxCardsIndicator`, `CheckboxCardsItem`, and `CheckboxCardsRoot`, to properly implement `forwardRef`. This will enable parent components to receive a ref to the underlying DOM elements of these components.

AI Summary: This issue proposes refactoring the `CheckboxIndicator` and `CheckboxRoot` components to utilize `forwardRef`. This change will enable parent components to receive a ref to the underlying DOM element of these checkbox sub-components.

AI Summary: This issue proposes refactoring the Callout component's sub-components—CalloutIcon, CalloutRoot, and CalloutText—to utilize `forwardRef`. This change is necessary to allow parent components to receive a ref to the underlying DOM element of these Callout parts.

AI Summary: This issue proposes refactoring the `Button` component to utilize `React.forwardRef`. The goal is to allow parent components to obtain a ref to the underlying DOM element of the Button, improving accessibility and control.

AI Summary: This issue is to refactor the `BlockQuote` component to use `forwardRef`. The goal is to allow parent components to pass refs directly to the underlying DOM element of `BlockQuote`.

AI Summary: This issue proposes refactoring the 'Badge' component to incorporate React's `forwardRef` functionality. The goal is to update the component to properly handle and pass down refs.

AI Summary: This issue proposes refactoring several sub-components of the AvatarGroup (AvatarGroupAvatar, AvatarGroupFallback, AvatarGroupItem, AvatarGroupRoot) to utilize `forwardRef`. The goal is to enable proper ref forwarding for these components.

AI Summary: This issue proposes refactoring the `AvatarFallback`, `AvatarImage`, and `AvatarRoot` components to incorporate React's `forwardRef` functionality. The goal is to enable these specific Avatar sub-components to properly forward refs to their underlying DOM elements.

AI Summary: This issue proposes refactoring the `AspectRatio` component to utilize `forwardRef`. This change will enable parent components to pass a ref down to the `AspectRatio` component, allowing direct access to its underlying DOM element or internal component.

AI Summary: This issue proposes refactoring all `AlertDialog` sub-components to utilize `React.forwardRef`. The task involves applying `forwardRef` to a list of nine specific components, including `AlertDialogAction`, `AlertDialogContent`, and `AlertDialogTrigger`, to enable proper ref forwarding.

AI Summary: This issue proposes refactoring five specific Accordion components (AccordionContent, AccordionHeader, AccordionItem, AccordionRoot, and AccordionTrigger) to utilize React's `forwardRef` API. The goal is to enable proper ref forwarding through these components.

AI Summary: This issue requests refactoring the `VisuallyHidden` component to properly support `forwardRef`. The task is part of a broader initiative to update components to correctly handle refs, requiring the component's definition to be wrapped with `React.forwardRef` and the ref passed down to its underlying element.

AI Summary: The `Card` component is currently missing `forwardRef` implementation, which is causing `Tooltip` components to break when used with `Card` in the `Tooltip` example. Adding `forwardRef` to the `Card` component is expected to resolve this issue.

AI Summary: Investigate whether the ScrollArea component is necessary within the Inline CodeHighlighter component of the Rad UI library. The issue suggests it might be redundant, causing unnecessary complexity. The task involves reviewing the code, testing the component's functionality without the ScrollArea, and potentially removing it if it doesn't impact functionality.

AI Summary: Debug and fix broken styles in the Rad UI ToggleGroup component, introduced in version 0.0.45 (likely since 0.0.43). The issue is related to pull request #1122 and involves inspecting the provided screenshot to identify and correct the styling problems.

AI Summary: The task involves fixing a copy-paste error in the documentation of a React UI library. Specifically, the description for an 'Icon' table in the documentation needs to be updated to reference the correct property (`api_documentation.icon.description`) instead of the incorrect one (`api_documentation.root.description`). This requires modifying a single line of code within a Markdown file (.mdx).

AI Summary: The task is to improve the portability of a pre-commit hook script by modifying how it sources shell configuration files. Instead of assuming the user uses zsh and sourcing ~/.zshrc directly, the script should check for the existence of common shell configuration files like ~/.zshrc and ~/.bashrc and source the appropriate one if found. This ensures compatibility across different shell environments.

AI Summary: Remove a leftover `*/}` from the Rad UI documentation for the Callout component located at https://www.rad-ui.com/docs/components/callout. This is a simple bug fix requiring editing the documentation.

AI Summary: Fix overlapping text in blockquote components of the Rad UI React library when multiple lines of text are present. This likely involves adjusting CSS styles to ensure proper line-height, padding, or margin within the blockquote element.