[pull] master from supabase:master#655
Merged
pull[bot] merged 3 commits intocode:masterfrom Feb 6, 2026
Merged
Conversation
…es (#42500) ## Context Related to FE-2461 Just following from the previous part [here](#41819) PR removes the usage of `useQueryStateWithSelect` in - Publishable API Keys (Delete) - Secret API Keys (Delete) - Auth Hooks (Edit) - Database Indexes (Edit + Delete) - Ensures that the appropriate behaviours are in place too - Toast should show when landing on a page with an invalid ID param that entity doesn't exist - Toast should not show when deleting the param (which useQueryStateWithSelect was using useRef as a workaround prior) ## To test - [ ] API keys (Both publishable and secret key) - URL updates when deleting a key - Refresh the page, delete dialog should open with the right key - Update the query param to something invalid, should see the "not found" toast - Delete a key, should only see a success toast - [ ] Auth Hooks - URL updates when adding / edit a hook - Refresh the page, panel should open with the right hook - Update the query param to something invalid, should see the "not found" toast - [ ] Database Indexes - URL updates when editing/deleting an index - Refresh the page, delete dialog should open with the right index - Update the query param to something invalid, should see the "not found" toast - Delete an index, should only see a success toast <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Bug Fixes** * Improved error handling and user notifications when API keys, hooks, or indexes are deleted or become unavailable; users now see clear toasts when a target item cannot be found. * **Refactoring** * Internal state and dialog visibility handling for API keys, hooks, and database indexes have been simplified to make UI flows more reliable and consistent. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Ali Waseem <waseema393@gmail.com>
## Context Replaces the provider name with the region code in the infrastructure settings overview node diagram - The latter is more important, and we don't really specify the cloud provider anywhere in the dashboard <img width="315" height="137" alt="Screenshot 2026-02-05 at 18 43 11" src="https://github.com/user-attachments/assets/bc6f4dab-e9be-4663-ae1e-50e76b517c86" /> Also made the same changes in the upcoming database replication page too in the form of tooltips And swapped the title + description to be more consistent (Top: type of data, bottom: description), same for the table below Before: <img width="737" height="335" alt="image" src="https://github.com/user-attachments/assets/6674564b-e871-4cd9-83a3-e0bfde7a9f83" /> <img width="287" height="354" alt="image" src="https://github.com/user-attachments/assets/f234de68-107b-470d-804a-bd3b1d9ae9dc" /> After: <img width="637" height="350" alt="image" src="https://github.com/user-attachments/assets/03e08d55-43a1-4a16-8be1-11dd7d14fef3" /> <img width="364" height="357" alt="image" src="https://github.com/user-attachments/assets/0e49df5b-68e5-4652-8dca-4d44ebb8c3ab" /> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Added region metadata with interactive tooltips across replication and database views. * Actions that modify replicas now refresh the list automatically. * Replication diagram layout updated with increased node spacing and a wider zoom-out range. * **Style** * Destination and replica name/ID display reorganized for clearer, two-line presentation. * BigQuery icon now inherits color from CSS for better visual consistency. * Provider/region labels refined for clearer wording. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Alaister Young <a@alaisteryoung.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )