flndrn 54c3812553 fix: Studio typecheck passes (0 errors) 2 hónapja
..
grid 717bd2b68b feat: platform proxy + Studio data layer for end-to-end table editor 2 hónapja
interfaces 54c3812553 fix: Studio typecheck passes (0 errors) 2 hónapja
layouts 54c3812553 fix: Studio typecheck passes (0 errors) 2 hónapja
to-be-cleaned c5aa765f6b feat(studio): fork supabase studio + rebrand to briven (phases 0-5.1) 3 hónapja
ui 54c3812553 fix: Studio typecheck passes (0 errors) 2 hónapja
ui-patterns c5aa765f6b feat(studio): fork supabase studio + rebrand to briven (phases 0-5.1) 3 hónapja
README.md c5aa765f6b feat(studio): fork supabase studio + rebrand to briven (phases 0-5.1) 3 hónapja

README.md

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-cleaned folder 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.tsx as 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

    ```ts

// Declare the prop types of your component interface ComponentAProps { sampleProp: string }

// Name your component accordingly const ComponentA = ({ sampleProp }: ComponentAProps) => { return

ComponentA: {sampleProp}
}

export default ComponentA ```