mirror of
https://github.com/supabase/supabase.git
synced 2026-10-08 19:05:06 +03:00
Claude
68d93eda83
- Register the warehouse_catalog integration overview in static-data/integrations/overviews.ts — the rebase brought in static-data/integrations/warehouse_catalog/overview.md without adding its entry to INTEGRATION_OVERVIEW_IDS, failing overviews.test.ts. - Run Prettier on 6 files left unformatted after resolving rebase conflicts (ConnectStepsSection.tsx, TableDetailDeleteTableSection.tsx, TableDetailIndexAdvisorSection.tsx, TableDetailOverview.utils.ts, TableDetailOverviewTab.tsx, EntityListItem.tsx).
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