mirror of
https://github.com/supabase/supabase.git
synced 2026-10-10 20:05:06 +03:00
Pamela Chia
3fc23db748
RequestUpgradeToBillingOwners now checks the requested plan against the viewer's current plan and renders a disabled state when the request would be a downgrade or no-op. This protects every callsite: the plan switcher (previously offered 'Request upgrade to Free' to higher-tier members), the log-drains empty state (hardcoded 'Pro' showing to Team members), the billing-metric paywall, and the custom-auth-providers fallback path. Addon-flavored requests (compute size, PITR, custom domain, IPv4, spend cap) bypass the guard because they are about feature add-ons, not plan tier changes.
Writing components
Where to create your components
- For components that declare the general structure and layout of a page:
/components/layouts/xxx
- For components that are tightly coupled to a specific interface:
/components/interfaces/xxx
- For components that are meant to be reusable across multiple pages:
/components/ui/xxx
- Note: We're gradually moving files out of the
to-be-cleanedfolder into the respective folders as we refactor
Component structure
- If a component has constants and utility methods that are tightly coupled to itself, keep them close to the component and enclose them in a folder with an
index.tsxas an entry point - Otherwise it can just be a file on its own
- For example:
-
components/ui - SampleComponentA - SampleComponentA.tsx - SampleComponentA.constants.ts - SampleComponentA.utils.ts - SampleComponentA.types.ts - index.ts - SampleComponentB.tsx
-
Template for building components
// Declare the prop types of your component
interface ComponentAProps {
sampleProp: string
}
// Name your component accordingly
const ComponentA = ({ sampleProp }: ComponentAProps) => {
return <div>ComponentA: {sampleProp}</div>
}
export default ComponentA