mirror of
https://github.com/supabase/supabase.git
synced 2026-10-13 21:29:08 +03:00
Claude
a747fa1eb4
The update endpoint replaces a bucket's whole lifecycle policy, and the form models only a one- or two-rule noncurrent-expiration policy, so saving a bucket configured through the S3 or Storage API dropped the rest of it. Detect a policy outside that shape, show it as read-only, and skip the write. A rejected retention policy also reported itself as a failed bucket creation, leaving the user to retry a name that now exists. Report it against the policy instead, and close the modal on the bucket that was in fact created. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01N3euXsz25sTybsGTcxCFfn
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>
}