Files
supabase/apps/studio/components
Gildas Garcia d4274ea27e Fix wrapper forms design (#46283)
## Screenshots

Before:
<img width="983" height="959" alt="image"
src="https://github.com/user-attachments/assets/b084ce4f-9ec8-4096-af02-b997d712edbb"
/>
<img width="472" height="962" alt="image"
src="https://github.com/user-attachments/assets/2ba5ccfd-71cc-4375-b87b-f74af64cec20"
/>

After:
<img width="1822" height="2632" alt="image"
src="https://github.com/user-attachments/assets/fa70bdd2-63c5-4259-aad5-d060f498a494"
/>
<img width="900" height="1120" alt="image"
src="https://github.com/user-attachments/assets/1d267828-c260-4220-9493-a28f012898f9"
/>


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Style**
* Clearer section separation using visual separators for wrapper
creation/edit flows.
  * Adjusted column selector sizing for improved responsiveness.
  * Secure fields show a loading state while retrieving secrets.

* **Refactor**
* Unified form section layout across wrapper management for more
consistent, scannable configuration panels.
* Simplified data-target and schema areas for easier navigation and
editing.

<!-- review_stack_entry_start -->

[![Review Change
Stack](https://storage.googleapis.com/coderabbit_public_assets/review-stack-in-coderabbit-ui.svg)](https://app.coderabbit.ai/change-stack/supabase/supabase/pull/46283?utm_source=github_walkthrough&utm_medium=github&utm_campaign=change_stack)

<!-- review_stack_entry_end -->
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2026-05-25 11:23:35 +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