dima/supabase

0 Fork 0

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

Files

T

Claude 0b4eec5066 feat(ui-patterns): add adaptiveHeight to PromptPanel; use it in Workers dialog

- PromptPanel: new `adaptiveHeight?: boolean` prop. When true, only the active
  TabsContent renders and the panel resizes to fit that tab. Default false
  keeps the existing stacked-in-one-grid-cell behavior so the docs homepage
  still gets a stable frame across tabs
- WorkerPromptPanel passes adaptiveHeight so the tabbed snippets in the
  Deploy-a-worker dialog size to whichever tab is active (AI Prompt is short,
  config.toml/cURL are taller)

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XQ5b58nwfCGsifA7PCheQb

2026-08-20 15:31:29 +00:00

scripts

chore: UI theme cleanup (#47519 )

2026-07-02 17:03:08 +02:00

src

feat(ui-patterns): add adaptiveHeight to PromptPanel; use it in Workers dialog

2026-08-20 15:31:29 +00:00

package.json

feat(studio): reuse docs PromptPanel in Workers empty state; rename Compute → Workers

2026-08-20 10:33:45 +00:00

README.md

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

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

tailwind.config.css

chore: Migrate the main Tailwind JS config to CSS (#45686 )

2026-05-13 13:14:58 +02:00

tsconfig.json

chore: Bump Typescript to v6 (#44204 )

2026-03-26 15:27:35 +01:00

vitest.config.ts

add coverage option to ui-patterns (#35669 )

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

vitest.setup.ts

chore: upgrade vite to v8 and vitest to v4 (#44833 )

2026-04-16 00:13:48 +09: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.