Joshen Lim
0c1bc80b89
## Context Related to this PR [here](https://github.com/supabase/supabase/pull/42265) If you were to update a cell twice, then save, the value that get's saved is the first edited value. There's a number of changes in this PR but the main thing is just `useOperationQueueActions` to declare `operations` outside of `handleSave` since `snap` wouldn't trigger the re-render of that function in the dependency array. ## Other changes - Refactored `useOperationQueueShortcuts.ts` - Reuse an existing `useHotKey` method to handle the event listeners - Remove unnecessary prop drilling, call the necessary hooks within it instead - Simplify its calling by only calling this hook within `SaveQueueActionBar` (removed calling from `OperationQueueSidePanel` - Add tooltip for OperatioItem "Remove operation" - (Unrelated) Fix Table Editor sort "Apply sort" CTA not working for large tables when applying sort on an indexed column (e.g primary key) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit ## Release Notes * **New Features** * Operation queue view now toggles open and closed with a single action * Simplified keyboard shortcuts: press **S** to save operations, **.** to toggle the queue view * **Bug Fixes** * Sort operations on large tables with non-primary-key sorting now show a confirmation warning and require explicit user approval before applying * **Improvements** * Operation queue panel automatically closes after successfully saving operations * Enhanced UI with improved delete action feedback and refined visual separators <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub> <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Supabase Studio
A dashboard for managing your self-hosted Supabase project, and used on our hosted platform. Built with:
What's included
Studio is designed to work with existing deployments - either the local hosted, docker setup, or our CLI. It is not intended for managing the deployment and administration of projects - that's out of scope.
As such, the features exposed on Studio for existing deployments are limited to those which manage your database:
- Table & SQL editors
- Saved queries are unavailable
- Database management
- Policies, roles, extensions, replication
- API documentation
Managing Project Settings
Project settings are managed outside of the Dashboard. If you use docker compose, you should manage the settings in your docker-compose file. If you're deploying Supabase to your own cloud, you should store your secrets and env vars in a vault or secrets manager.
How to contribute?
- Branch from
masterand name your branches with the following structure{type}/{branch_name}- Type:
chore | fix | feature - The branch name is arbitrary — just make sure it summarizes the work.
- Type:
- When you send a PR to
master, it will automatically tag members of the frontend team for review. - Review the contributing checklists to help test your feature before sending a PR.
- The Dashboard is under active development. You should run
git pullfrequently to make sure you're up to date.
Developer Quickstart
Note
Supabase internal use: To develop on Studio locally with the backend services, see the instructions in the internal
infrastructurerepo.
# You'll need to be on Node v20
# in /studio
## For external contributors
pnpm install # install dependencies
pnpm run dev # start dev server
## For internal contributors
## First clone the private supabase/platform repo and follow instructions for setting up mise
mise studio # Run from supabase/platform alongside `mise infra`
## For all
pnpm run test # run tests
pnpm run test -- --watch # run tests in watch mode
Running within a self-hosted environment
Follow the self-hosting guide to get started.
cd ..
cd docker
docker compose -f docker-compose.yml -f ./dev/docker-compose.dev.yml up
Once you've got that set up, update .env in the studio folder with the corresponding values.
POSTGRES_PASSWORD=
SUPABASE_ANON_KEY=
SUPABASE_SERVICE_KEY=
Then run the following commands to install dependencies and start the dashboard.
npm install
npm run dev
If you would like to configure different defaults for "Default Organization" and "Default Project", you will need to update the .env in the studio folder with the corresponding values.
DEFAULT_ORGANIZATION_NAME=
DEFAULT_PROJECT_NAME=