chore: refactor Button API so that it can be used a standard button (#46880)

## Problem

Our `<Button>` component breaks the default `button` contract by
redefining the `type` prop to set its variant (`primary`, `default`,
etc) instead of the button type (`submit`, `button`, etc).
This is confusing and forces to write more code when using it with
shadcn components that expect/inject the standard button props.

## Solution

- rename the `type` prop to `variant`
- rename the `htmlType` prop to `type`
- propagate the changes where necessary
- format code

## How to test

As this is just prop renaming, if it builds it's ok

---------

Co-authored-by: Ivan Vasilov <vasilov.ivan@gmail.com>
This commit is contained in:
Gildas GarciaandIvan Vasilov authored and GitHub committed 2026-06-16 23:59:58 +02:00
1 parent 608040b8cb
commit 96d43099bb
1105 files changed
+2713 -2545

No files matched your search

+1 -1
View File
@@ -53,7 +53,7 @@ export function CommandMenu({ ...props }: DialogProps) {
return (
<>
<Button
type="outline"
variant="outline"
className={cn(
`relative h-8 w-full justify-start rounded-[0.5rem] bg-background text-sm font-normal text-foreground-muted shadow-none sm:pr-12
hover:border-foreground-muted hover:bg-surface-100 hover:text-foreground-lighter