Files
supabase/apps/studio/components/layouts/AppLayout/EnableBranchingButton/BranchingPostgresVersionNotice.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

35 lines
1.2 KiB
TypeScript

import { useParams } from 'common'
import { AlertCircleIcon } from 'lucide-react'
import Link from 'next/link'
import { Alert, AlertDescription, AlertTitle, Button } from 'ui'
import { useAppStateSnapshot } from '@/state/app-state'
export const BranchingPostgresVersionNotice = () => {
const { ref } = useParams()
const snap = useAppStateSnapshot()
return (
<Alert className="rounded-none px-7 py-6 [&>svg]:top-6 [&>svg]:left-6 border-t-0! border-l-0! border-r-0!">
<AlertCircleIcon />
<AlertTitle className="text-base">
Your project needs to be on Postgres 15 to enable branching
</AlertTitle>
<AlertDescription>
Head over to your project's infrastructure settings to upgrade to the latest version of
Postgres before enabling branching.
</AlertDescription>
<AlertDescription>
<Button size="tiny" variant="default" className="mt-4">
<Link
href={`/project/${ref}/settings/infrastructure`}
onClick={() => snap.setShowCreateBranchModal(false)}
>
Head to project settings
</Link>
</Button>
</AlertDescription>
</Alert>
)
}