Files
supabase/apps/studio/components/interfaces/JwtSecrets/start-using-keys-banner.tsx
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

30 lines
929 B
TypeScript

import { Import } from 'lucide-react'
import { Button } from 'ui'
import { FeatureBanner } from '@/components/ui/FeatureBanner'
export const StartUsingJwtSigningKeysBanner = ({
onClick,
isLoading,
}: {
onClick: () => void
isLoading: boolean
}) => {
return (
<FeatureBanner bgAlt>
<div className="flex flex-col gap-0 z-2">
<p className="text-sm text-foreground">Start using JWT signing keys</p>
<p className="text-sm text-foreground-lighter lg:max-w-sm 2xl:max-w-none">
Right now your project is using the legacy JWT secret. To start taking advantage of the
new JWT signing keys, migrate your project's secret to the new set up.
</p>
<div className="mt-4">
<Button variant="primary" icon={<Import />} onClick={onClick} loading={isLoading}>
Migrate JWT secret
</Button>
</div>
</div>
</FeatureBanner>
)
}