mirror of
https://github.com/supabase/supabase.git
synced 2026-10-08 02:45:07 +03:00
Charis
2f4f0adbd1
Refactor tabs so that: - Behavior add-ons, such as query params, are HOCs in ui-patterns, to keep the basic Tabs minimal - No dependency on next/router (this is to smooth out a separate App Router migration PR) - No dependency on useSearchParams either (this is to preserve static generation of as much HTML content as possible, for SEO purposes -- see comment about client-rendering bailout when using useSearchParams) - Syncing behavior better localized in a hook Minor enhancement to save tab preferences to local storage so they are remembered between sessions
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