mirror of
https://github.com/supabase/supabase.git
synced 2026-10-13 21:29:08 +03:00
Claude
eb64004f4c
Create modal: expiration inputs default to 30 days and 10 versions instead of empty, so toggling versioning on surfaces a policy that's ready to save. Clearing a field still removes that condition from the policy. Edit modal: same defaults, but only when the bucket has never had versioning enabled — buckets already versioned keep their existing values (including explicit null == "no limit on this condition"), so the modal never silently retro-adds a condition the user removed.
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 — use a named export, not a default export
export const ComponentA = ({ sampleProp }: ComponentAProps) => {
return <div>ComponentA: {sampleProp}</div>
}