mirror of
https://github.com/supabase/supabase.git
synced 2026-10-07 10:25:06 +03:00
* improve table editor headers * sql editor horizontal scroll auto in headers * fix headers in tablelist * fix headers in db roles * fix database functions in smol screens * fix table list headers * fix trigger lists table * fix enum types headers * Update Extensions component styling with flex-wrap * Update Indexes component UI layout and styling * fix publications table * move sql editor pagination tobottom * rm unused imports, add correct label to db selector * fix layout shift in run button * add tooltip to results limitter * make header in sql editor results scrollable * Fix Button tooltip and table header formatting for database/tables/[id] ColumnList * Fix SQL editor footer disappearing with resizable panel --------- Co-authored-by: Joshen Lim <joshenlimek@gmail.com>
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