mirror of
https://github.com/supabase/supabase.git
synced 2026-10-13 21:29:08 +03:00
Danny White
a42433c9bd
## Problem The pipeline creation wizard in #49243 needs destination connection settings on its connection step, separately from replication settings and table layout. These fields currently live inside the sheet’s Advanced settings accordion. ## Solution Extract BigQuery’s **Connection pool size** and **Maximum staleness**, DuckLake’s **Pool size**, and Snowflake’s optional **Role** into reusable connection-field components. Keep the existing accordion as their first consumer. Labels, defaults, units, field order and empty-value handling stay the same. ## Review instructions 1. Open the [preview to Database → Pipelines](https://studio-staging-git-dnywh-refactorpipeline-conne-4a9108-supabase.vercel.app/dashboard/project/_/database/pipelines), select a test project with Pipelines enabled and click **Add pipeline**. Keep BigQuery selected and expand **Advanced settings**. 2. Confirm **Connection pool size** and **Maximum staleness** still appear below **Invalidated slot behavior** and above **Table layout**, with the same descriptions and the **connections** and **minutes** units. 5. Select DuckLake, if available, and expand **Advanced settings**. Confirm **Pool size** remains above **Batch wait time**, with its existing description and 1–6 limits. 6. Select Snowflake, if available, and expand **Advanced settings**. Confirm optional **Role** remains below **Invalidated slot behavior**, with the `PIPELINES_ROLE` placeholder.
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>
}