dima/supabase

0 Fork 0

mirror of https://github.com/supabase/supabase.git synced 2026-10-14 13:49:09 +03:00

Files

T

Francesco Sansalvadore 4b7367b004 fix(studio): org project card z-index (#42424 )

## What kind of change does this PR introduce?

Fix project card z index issue.

## What is the current behavior?

<img width="718" height="573" alt="Screenshot 2026-02-03 at 18 32 40"
src="https://github.com/user-attachments/assets/565e397d-6cfb-4d66-8b79-7cf21019fc4f"
/>

## What is the new behavior?

<img width="344" height="405" alt="Screenshot 2026-02-03 at 18 32 22"
src="https://github.com/user-attachments/assets/6969e581-dc44-42c0-b144-216be66b33f1"
/>

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

## Summary by CodeRabbit

* **Refactor**
* Updated project card component structure and styling for improved
layout consistency.
  * Enhanced project status display presentation on project cards.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

2026-02-04 10:32:25 +00:00

grid

fix: AI filter re-render by seperating URL logic syncing and local state (#42396 )

2026-02-03 17:34:22 +00:00

interfaces

fix(studio): org project card z-index (#42424 )

2026-02-04 10:32:25 +00:00

layouts

chore: change primary button for resumes (#42436 )

2026-02-04 10:55:55 +05:30

to-be-cleaned

chore(studio): filter policies by bucket name (#40456 )

2025-11-14 17:47:16 +08:00

refactor new homepage usage (#42394 )

2026-02-04 09:43:01 +01:00

README.md

Final replacements of ui setNotification with toast (#21885 )

2024-03-12 12:56:56 +08:00

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


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