dima/supabase

0 Fork 0

mirror of https://github.com/supabase/supabase.git synced 2026-10-11 04:15:04 +03:00

Files

T

Danny White e8b5b565a9 chore(design-system): centralise MCP client assets (#43730 )

## What kind of change does this PR introduce?

Chore

## What is the current behavior?

- We use the MCP client connect dialog in two places: Studio and Docs
- We duplicate image assets for each client in each of those two places

## What is the new behavior?

- Centralised assets
- Consolidation and simplification as a result of it all being a single
source-of-truth now

## To test

- [ ] Everything works as it did before across both Studio and
[Docs](https://supabase.com/docs/guides/getting-started/mcp)
- [ ] All MCP client images load as expected

2026-03-17 11:19:49 +11:00

scripts

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

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

src

chore(design-system): centralise MCP client assets (#43730 )

2026-03-17 11:19:49 +11:00

index.tsx

feat(design-system): status code component (#42064 )

2026-03-12 10:57:46 +00:00

package.json

feat: improve db overload debugging UX (#43564 )

2026-03-16 11:22:30 +01: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.