Files
supabase/apps/studio/components/interfaces/Integrations/Integration/MissingExtensionAlert.tsx
Gildas Garcia 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

32 lines
953 B
TypeScript

import { useState } from 'react'
import { Button } from 'ui'
import { EnableExtensionModal } from '@/components/interfaces/Database/Extensions/EnableExtensionModal'
import { DatabaseExtension } from '@/data/database-extensions/database-extensions-query'
export const MissingExtensionAlert = ({ extension }: { extension: DatabaseExtension }) => {
const [showEnableExtensionModal, setShowEnableExtensionModal] = useState(false)
const extensionInstalled = !!extension?.installed_version
if (!extensionInstalled) {
return (
<>
<Button
variant="primary"
className="w-min"
onClick={() => setShowEnableExtensionModal(true)}
>
Enable {extension.name}
</Button>
<EnableExtensionModal
visible={showEnableExtensionModal}
extension={extension}
onCancel={() => setShowEnableExtensionModal(false)}
/>
</>
)
}
return null
}