Files
supabase/apps/docs/content/_partials/uiLibCta.mdx
Gildas GarciaandIvan Vasilov 96d43099bb 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>
2026-06-16 23:59:58 +02:00

10 lines
286 B
Plaintext

<Admonition type="tip" title="Explore drop-in UI components for your Supabase app.">
UI components built on shadcn/ui that connect to Supabase via a single command.
<Button variant="primary" asChild>
<a href="https://supabase.com/ui">Explore Components</a>
</Button>
</Admonition>