Files
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

34 lines
823 B
TypeScript

import { useState } from 'react'
import { Button } from 'ui'
import { NewScopedTokenSheet } from './NewScopedTokenSheet'
import { type NewScopedAccessToken } from '@/data/scoped-access-tokens/scoped-access-token-create-mutation'
export interface NewScopedTokenButtonProps {
onCreateToken: (token: NewScopedAccessToken) => void
}
export const NewScopedTokenButton = ({ onCreateToken }: NewScopedTokenButtonProps) => {
const [visible, setVisible] = useState(false)
return (
<>
<Button
variant="primary"
onClick={() => {
setVisible(true)
}}
>
Generate new token
</Button>
<NewScopedTokenSheet
visible={visible}
onOpenChange={setVisible}
tokenScope={undefined}
onCreateToken={onCreateToken}
/>
</>
)
}