dima/supabase

0 Fork 0

mirror of https://github.com/supabase/supabase.git synced 2026-10-09 19:35:06 +03:00

Files

T

Ali Waseem 818cbd36fd fix: new filter updates in table editor better mobile view (#43604 )

## 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?

Right now the new filter bar just does not work on mobile. It fully
collapses and does not appear correctly. This make it stack on smaller
screens and shows it to be visible. Works on smaller tabs

Note: there is a bit of awkwardness on certain screen sizes where its
one long row, will fix that later. This is better than nothing right now

2026-03-10 23:26:58 +01:00

scripts

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

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

src

fix: new filter updates in table editor better mobile view (#43604 )

2026-03-10 23:26:58 +01:00

index.tsx

feat(studio): mobile sheet nav (#43184 )

2026-02-27 12:06:27 +00: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.