mirror of
https://github.com/supabase/supabase.git
synced 2026-10-07 02:15:05 +03:00
Ivan Vasilov
b77a1b48be
* initial test. * Add base path to the rewrites. * Remove base path from the source rewrite. * Another try. * Another try. * another try. * Try another magic. * Add try/catch to the flag processing code. * Revert some of the unneeded changes. * Fix the api route for flags. * Remove vercel/toolbar for local dev. * Try using a static file for toolbar config. * Add a well known flags file in the www app. * Add headers to interpret vercel/flags as json. * Another try. * Fix the json formatting. * Add headers for the vercel/flags route in the www app. * Change to force studio to deploy.
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