mirror of
https://github.com/supabase/supabase.git
synced 2026-10-12 21:05:06 +03:00
Benjamin
78131dbc7b
- Add useIsWarehouseEnabled (useFlag('warehouse')) and gate every warehouse
surface: the table Storage section, per-table chips/badges (via the data
selectors' query `enabled`), the Warehouse Catalog integration listing, and
the Connect-sheet catalog tab. Defaults off until the flag is registered.
- Rework Warehouse Catalog credentials from the prototype's Iceberg-REST triple
to the real DuckLake-on-Supabase shape: the current project is used for both
catalog (its Postgres) and storage (its bucket), surfaced as
catalogUrl + dataPath + s3* + metadataSchema. Snippet becomes a DuckDB
`ATTACH 'ducklake:...'` config + raw env vars (engines reduced to DuckDB + env).
- Update WAREHOUSE_API_PLAN.md catalog endpoint to the resolved DuckLake design.
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