mirror of
https://github.com/supabase/supabase.git
synced 2026-10-10 11:55:05 +03:00
Gildas GarciaandIvan Vasilov
96d43099bb
## 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>
29 lines
918 B
TypeScript
29 lines
918 B
TypeScript
import { useParams } from 'common'
|
|
import Link from 'next/link'
|
|
import { Button } from 'ui'
|
|
import { Admonition } from 'ui-patterns'
|
|
|
|
const PublicSchemaNotEnabledAlert = () => {
|
|
const { ref: projectRef } = useParams()
|
|
|
|
return (
|
|
<Admonition type="default">
|
|
<p className="mt-0! mb-1.5!">The public schema for this project is not exposed</p>
|
|
<p className="mt-0! mb-1.5! text-foreground-light">
|
|
You will not be able to query tables and views in the public schema via supabase-js or HTTP
|
|
clients. Configure this behavior in your project's Data API settings.
|
|
</p>
|
|
<Button asChild variant="default" className="mt-1">
|
|
<Link
|
|
href={`/project/${projectRef}/settings/api#postgrest-config`}
|
|
className="no-underline!"
|
|
>
|
|
View API settings
|
|
</Link>
|
|
</Button>
|
|
</Admonition>
|
|
)
|
|
}
|
|
|
|
export default PublicSchemaNotEnabledAlert
|