Files
supabase/studio/components
Joshen LimandTerry Sutton 69d16750a6 Feat/enum types management (#17953)
* Set up react queries for enumerated types

* Add delete enumerated type RQ

* Implement types UI + deleting types

* Implement create enumerated type

* Implement update enumerated type

* Tidy enumb dropdown in table editor

* Fix default value dropdown for enum in column editor

* Remove unused code

* Add create enum type cta in column editor

* Support updating enum description

* Add learn more URL RE inability to delete a single enum value

* Add sorting when creating enums

* Support updating existing values in an enum type

* Support updating order when editing existing enum

* Address comments part 1

* Address comments part 2

* Use lucide icons

* Update icons

* Address comments part 3

* Refactor enum type forms to use react hook form

* Update studio/components/interfaces/Database/EnumeratedTypes/EditEnumeratedTypeSidePanel.tsx

* Update studio/components/interfaces/Database/EnumeratedTypes/EditEnumeratedTypeSidePanel.tsx

* Copy

* Small style fix to API panel

* Use new input components and add alert when creating enum type

* Address comments

* Address comments

---------

Co-authored-by: Terry Sutton <saltcod@gmail.com>
2023-10-10 14:08:29 +08:00
..
Fix
2023-08-28 13:37:19 +08:00
2023-10-10 14:08:29 +08:00
2023-08-07 13:56:43 +08: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

import { observer } from 'mobx-react-lite'

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

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

// Observer is so that components listen to mobx store changes
export default observer(ComponentA)