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

40 lines
1.2 KiB
TypeScript

import { useState } from 'react'
import { Button } from 'ui'
import { Admonition } from 'ui-patterns'
import { usePgPartmanStatus } from '../usePgPartmanStatus'
import { EnableExtensionModal } from '@/components/interfaces/Database/Extensions/EnableExtensionModal'
export function PgPartmanCallout() {
const { pgPartmanExtension, isAvailable, isInstalled } = usePgPartmanStatus()
const [showEnableModal, setShowEnableModal] = useState(false)
if (!isAvailable || isInstalled) return null
return (
<div className="mx-5 my-2">
<Admonition
type="tip"
title="pg_partman is now available"
description="Unlock partitioned queues for automatic data retention, lower storage costs, and faster performance at scale."
>
<Button
variant="default"
size="tiny"
className="mt-2"
onClick={() => setShowEnableModal(true)}
>
Enable pg_partman
</Button>
</Admonition>
{pgPartmanExtension && (
<EnableExtensionModal
visible={showEnableModal}
extension={pgPartmanExtension}
onCancel={() => setShowEnableModal(false)}
/>
)}
</div>
)
}