dima/supabase

0 Fork 0

mirror of https://github.com/supabase/supabase.git synced 2026-10-12 12:55:06 +03:00

Files

T

History

Ali Waseem 1ed4ea0c60 fix: updated styling based on feedback (#42694 )

## I have read the
[CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md)
file.

YES

## What kind of change does this PR introduce?

small: Update styling for filters based on internal feedback

## Demo
<img width="286" height="307" alt="Screenshot 2026-02-11 at 8 52 18 AM"
src="https://github.com/user-attachments/assets/fb7b6b01-a1c3-47be-b979-2dd774f535ca"
/>



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

* **Style**
* Simplified FilterBar item layout: operator symbol now appears inline
after labels and the right-side check indicator has been removed.
  * Filter headers use bolder text weight for improved hierarchy.
* Operator badges use a lighter foreground color for better visual
contrast and consistency.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

2026-02-11 10:33:55 -07:00

scripts

chore: Migrate studio to use ui-patterns/shimmeringLoader (#41405 )

2025-12-17 14:54:07 +01:00

src

fix: updated styling based on feedback (#42694 )

2026-02-11 10:33:55 -07:00

index.tsx

Add read replicas details page from database replication (#41784 )

2026-01-19 13:44:41 +08:00

package.json

Connect sheet content structure (#42373 )

2026-02-11 13:32:45 +08:00

README.md

feat: Move some components into ui-patterns (#20774 )

2024-02-12 12:44:00 +01:00

tailwind.config.js

SQL to REST translator (#25978 )

2024-05-22 12:37:01 -06:00

tsconfig.json

chore: Move the files in ui-patterns under src folder (#36032 )

2025-05-30 12:46:22 +03:00

vitest.config.ts

add coverage option to ui-patterns (#35669 )

2025-05-29 19:09:26 +02:00

vitest.setup.ts

chire: Sort imports in all packages, cms, design-system and ui-library apps (#41610 )

2026-02-05 13:54:10 +01:00

README.md

Supabase UI Patterns

This package should be used for components which are built using NPM libraries (react-markdown, reactflow for example), which make no sense to be included in all apps. It should also be used for components which are constructed using various components from the ui package.

This package does not have a barrel file - each component has to be imported from its index (ui-patterns/PrivacySettings, for example). This is intentional so that adding a new component which is used only in 1 or 2 apps doesn't burden the rest of the apps.