mirror of
https://github.com/supabase/supabase.git
synced 2026-07-06 04:54:23 +08:00
221ee13f79
* Refactor and remove the CreateFunctionStore. * Fix a duplicate key in the functions table. * More fixes for the create-function form. * Add excluded schemas to schema selector. * Cleanup the createFunction code after the merge. * Remove unneeded wrapper fragments. * Minor fixes for the FormItemLayout stories. * Refactor the CreateFunction panel using the new FormItemLayout. * Revert the migration to use FormItemLayout. Will revisit later. * Add a CSS class for popover content width to match its trigger width. Use it on the schema selector. * Replace all listboxes with selects. * Fix the comments. * Switch to FormItemLayout wherever possible. * Move the createFunction file to its own folder. * Refactor the panel to use shadcn components: Sheet, SheetContent and SheetHeader. * Add showClose prop to the Sheet component. * Add function editor and a feature to maximize/minimize the code editor. * Some fixes * Add sameWidthAsTrigger to the popover component. * Fix the icon size. --------- Co-authored-by: Jonathan Summers-Muir <MildTomato@users.noreply.github.com> Co-authored-by: Joshen Lim <joshenlimek@gmail.com>
Styles
When to write custom styles
Tailwind should be sufficient to cover the majority of styling needs. We typically only write custom styles here in the event where we're working with an external library and we need to override some styles (e.g Monaco, or even our own UI library).
Ideally, keep custom styling here to a minimum, use tailwind directly in the pages and components where possible, so that we have less code to maintain.
If you're writing custom styles
Group custom styles into separate stylesheets based on their context. For styles which are generic and global, we can write them in main.scss.