Files
supabase/apps/studio/components
Francesco SansalvadoreandClaude Sonnet 5 b8d03d2214 feat(storage): wire object versioning into the bucket modals
Mounts the versioning form section in the create and edit bucket modals behind
`useIsStorageVersioningEnabled`. Form state only for now — the Storage API does
not accept the fields yet, and both call sites are marked with TODOs.

- Both modals spread `bucketVersioningFormFields` into their schema and call
  `superRefineBucketVersioning` from `superRefine`
- Create prefills the project defaults (30 days / 10 versions)
- Edit adds a confirmation before suspending an actively versioning bucket, and
  derives its prefill through `getVersioningFormDefaults`
- `EditBucketModal.utils.ts` replaces the prefill and next-state derivations
  with pure, tested helpers instead of stacked nested ternaries
- `storage_bucket_created` now reports whether versioning was enabled

Both forms move to `mode: 'onChange'` so the numeric versioning bounds surface as
the user types rather than only on submit. This also replaces the prototype's
`trigger()`-inside-`onChange`, which validated against pre-update form state.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-10-05 15:04:12 +02:00
..

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-cleaned folder 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.tsx as 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>
}