Files
supabase/apps/studio/components
Francesco SansalvadoreandJordi Enric 715b83b124 chore: realtime reports (#36797)
* init realtime reports page

* realtime metrics

* remove mock

* rebase branch

* chore: add realtime_postgres_changes infra-monitoring query

* clean realtime config

* clean realtime config

* test queries

* fix duplicate values

* update realtime charts components

* update realtime charts types

* update realtime charts types

* restore realtime charts logic

* add realtime charts

* hide redundant refresh and datepicker

---------

Co-authored-by: Jordi Enric <jordi.err@gmail.com>
2025-07-03 18:14:19 +02:00
..
2025-07-03 13:43:24 +02:00
2025-07-03 18:14:19 +02:00
2025-07-03 13:43:24 +02: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