[pull] master from supabase:master #668
Merged
Conversation
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
This is part two of a [PR breakdown](#42276) that introduces our connect schema and how content is retrieved. This focuses on the Framework tab to start. Fields are generated and content is rendered using a connect.schema file. This schema file defines modes, fields and steps. Each mode has a set of fields. Each field can be dependent on another field. The steps generated are then based off the values of the modes and fields. Each step can also render varying content dynamically using a template {{framework}}/{{frameworkVariant}}/{{library}} which just replaces those values with what's in state (fields selected). [Part one needs to be merged first.](#42367) The next stage will add back all other tabs and content. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * New Connect Sheet UI to guide app-to-project connections with dynamic configuration and copyable connection parameters. * Multi-framework & mobile support with ready-to-use code examples, install commands, and step-by-step setup for 20+ frameworks. * Multiple PostgreSQL connection methods (direct, transaction, session) with safe/masked connection previews. * Copy-prompt that aggregates step content and code for easy sharing. * **UI** * Multi-file code viewer with tabbed code blocks and added syntax support (Swift, TOML, HTML). * **Tests** * Comprehensive unit tests for resolver and state logic. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Joshen Lim <[email protected]>
## What kind of change does this PR introduce? - ~Feat~ Chore - Resolves DEPR-33 ## What is the current behavior? The dialog used to delete an organization uses a ”type this org’s name in before you can press this button” interaction but: - A) Enables the button the whole time - B) We already have this componentized in TextConfirmModal ## What is the new behavior? - Refactored this dialog to use `TextConfirmModal` instead - Updated design docs to make this prop clearer | Before | After | | --- | --- | | <img width="1024" height="759" alt="Supabase" src="https://github.com/user-attachments/assets/85c965f6-29d4-4696-8c0c-a54ddcbe6167" /> | <img width="1024" height="759" alt="Supabase" src="https://github.com/user-attachments/assets/0a96ca65-15c3-4b1b-bb10-620526c059b8" /> | <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Updated Text Confirm Dialog documentation with clarifications: the confirm action remains disabled until input exactly matches the required string, and leading/trailing whitespace is trimmed from the input. * **Refactor** * Streamlined the organization deletion confirmation workflow for improved user experience. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
## What kind of change does this PR introduce? - Chore - Resolves DEPR-163 ## What is the current behavior? 1Password and other password managers’ widgets pop up in the _Name_ `input` despite that being irrelevant to password managers. ## What is the new behavior? We tell that field to ignore password mangers. ## Additional context Apple’s own password manager does not have an attribute and the secret value is password-like, so I’m unable to hide theirs. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Improved form behavior with password managers by updating input configuration settings on the edge function secrets form. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
## What kind of change does this PR introduce? - Fix - Resolves DEPR-334 ## What is the current behavior? Not enough colour contrast on selected item. It’s hard to tel what’s selected, especially on light mode. ## What is the new behavior? Updated the storage explorer row styling to use `bg-selection` for selected, opened, and previewed rows, which increases contrast in light mode. | Before | After | | --- | --- | | <img width="1166" height="759" alt="Buckets Supabase-60C5BBB5-FB94-44AA-9435-E9610ACB25AA" src="https://github.com/user-attachments/assets/4f6071eb-70de-4389-89bf-3f3d127d32a9" /> | <img width="1166" height="759" alt="Buckets Supabase" src="https://github.com/user-attachments/assets/7c3d7f53-a340-4718-8224-e5a3bb184181" /> | <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Style** * Updated file explorer row background styling to provide consistent visual feedback for opened, previewed, and selected item states in the storage interface. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Context For UI consistency - use `OrganizationCard` component for org wildcard route as per the /organizations page ### Before <img width="1228" height="501" alt="image" src="https://github.com/user-attachments/assets/0a7442f0-d041-4657-9142-c475dbca630c" /> ### After <img width="1216" height="328" alt="image" src="https://github.com/user-attachments/assets/795a39f5-70ea-4681-b087-845fd022ae60" /> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Bug Fixes** * Fixed URL generation to avoid dangling or empty query strings when navigating organizations. * **Refactor** * Replaced previous button-based organization items with card-based organization components for a cleaner presentation. * Deferred organization data initialization until after navigation query computation to ensure correct results. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES ## What kind of change does this PR introduce? Documentation update ## What is the current behavior? `https://supabase.com/humans.txt` does not have Tanun's name ## What is the new behavior? `https://supabase.com/humans.txt` will have Tanun's name <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Updated team member information in public team listing. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
…ABLE_KEY` for all blocks (#42652) This PR renames all `SUPABASE_PUBLISHABLE_OR_ANON_KEY` env vars into `SUPABASE_PUBLISHABLE_KEY` to make the new API keys default. This is in coordination with the rest of the docs. I've also cleaned up the `blocks/vue` package from unused files. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Breaking Changes** * Public environment variable names renamed from PUBLISHABLE_OR_ANON_KEY → PUBLISHABLE_KEY across all framework integrations; update your environment configs. * **Documentation** * All framework guides, .env examples and registry docs updated to use the new variable names. * **Chores** * Cleaned up UI registry/templates: some example Vue registry items and autogenerated registry artifacts were removed or simplified. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
6 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 : )