mirror of
https://github.com/supabase/supabase.git
synced 2026-10-09 03:15:06 +03:00
Claude
f732560823
Renames the noun phrase that names the policy object — the section heading in the create/edit bucket modals, the file preview panel tooltip title, the empty-state copy in the archived / trash views, and the internal ExpirationPolicySection component — to "lifecycle policy", matching S3's own terminology. Preserves verb / action-form uses of expire/expiration where they describe what happens when the policy fires (ExpirationSentence, ExpirationExplainer, ExpirationMode, version_expiry_days, "Noncurrent version expiration" label, etc.) — those name the action, not the policy.
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>
}