Files
supabase/apps/studio/components
Terry Sutton 50ede5546f Chore/webhook json (#30797)
* Enforce json payloads with webhook jobs

* EFs need json as well

* Handle case where the body can be null/undefined.

* Fix url in the child id.

* Fix a redirect for cron.

---------

Co-authored-by: Ivan Vasilov <vasilov.ivan@gmail.com>
2024-12-03 09:05:56 -03:30
..
2024-12-03 09:05:56 -03:30
2024-12-03 09:05:56 -03:30
2024-12-03 09:23:37 +01:00

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


// 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