* refactor(components): remove redundant empty interfaces from Input, Command, and Textarea components
Simplified props handling by removing redundant empty interfaces (`InputProps`, `CommandDialogProps`, `TextareaProps`). Directly extended native HTML attributes/lib for each component, enhancing code clarity and maintainability. This refactor ensures compliance with ESLint rules and streamlines future modifications without altering component functionality.
* updated the registry
* rerun build:registry with updated command
* Refactor input and textarea components to use `React.ComponentProps`
* update registry
* refactor(sidebar): improve setOpen callback logic
- Simplify state handling
- Ensure consistent cookie setting
- Added ability for users to persist sidebar state via cookies
- Update sidebar.mdx doc with SSR persistence instructions
- Run pnpm registry:build to update component
* docs: updates
---------
Co-authored-by: shadcn <m@shadcn.com>
The text-sidebar-foreground class was applied to the SidebarProvider, which is designed to wrap the whole app, therefore making the whole app inherit its font color. This has been removed. The correct place for it is in the Sidebar component
Of the 3 possible return cases in the Sidebar component, 2 already applied the text-sidebar-foreground and I have added it to the third
* fix: fix breaking changes for Command component that comes with cmdk 1.0.0
* chore: build registry
* chore: moving paths for some examples
* chore: moving paths for some examples
* chore: use data instead of aria
* fix: update command and pin cmdk
* fix: model selector
* fix: command for new york
---------
Co-authored-by: shadcn <m@shadcn.com>
# Current Issue
when running `next lint`, the typescript compiler fails on the chart component (closes#4229 )
`Type error: Type 'string[]' is not assignable to type 'string | TrustedHTML'.`
# Resolution
We can coerce the `string[]` into a valid type by `join`ing.
Data attributes at <CommandPrimite.List /> component should be written as data-[disabled=true] in order to avoid styles being applied to element, even when it's not disabled.
* feat: add input-otp
* feat: update input-otp and add examples
* feat(input-otp): add controlled and form examples
* chore(input-otp): update to latest
* docs(www): fix example code for input-otp
* fix(www): disable menu
Resolves#2025
This adds the "use client" directive to the Toast component, since it makes use of client-only features like `useState`. When absent, this causes errors in rendering as described in the issue.
[Reopen a PR that was accidentally closed.](https://github.com/shadcn-ui/ui/pull/2233)
carousel, resizable components to be used by the app router, a "use client" directive is required.
This PR replaces the maximum id from `Number.MAX_VALUE` to `Number.MAX_SAFE_INTEGER` in `use-toast.ts`. Considering how JS stores numbers, it's unsafe to plus one if the number is larger than `Number.MAX_SAFE_INTEGER`. Here is an example:
```js
> let num
> num = Number.MAX_VALUE - 1
> num + 1 === num
true
> num = Number.MAX_SAFE_INTEGER - 1
> num + 1 === num
false
```
* feat: added toggle-group component
* fix(components): ran build:registry script
* fix(components): fixed colors in toggle-group
- Dark mode border color is now consistent with the toggle component
* fix(components): fixed component.json toggle-group
- Added the content field to `components.json` for toggle-group
- Ran build:registry again
* feat(toggle-group): simplify implementation
---------
Co-authored-by: shadcn <m@shadcn.com>
In order to have a smooth opening of the accordion, moving the `AccordionContent` `className` overwrite to the children wrapper component allow Radix to calculate correctly the animation and execute a smooth animation in case of `className` on the `AccordionContent` component.
Possibly related to https://github.com/shadcn-ui/ui/issues/944
This pull request resolves#1686.
## Rationale for this PR
This PR affects the code for `RadioGroupItem` in both styles by removing the `children` prop from the component. The children prop is automatically passed in by the use of the spread operator (`...props`) and is redundant because it is never used in the component.
This PR shouldn't affect tests, representation, etc. and is merely a cosmetic change. There is no urgent need to merge this.
