[pull] master from supabase:master #244
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
We are missing support for tags in typespec v0.23+. Tags such as `@experimental` are now in the modifierTags array on the Comment class. Map these into the old format so it remains compatible.
Migrate workflows to Blacksmith Co-authored-by: blacksmith-sh[bot] <157653362+blacksmith-sh[bot]@users.noreply.github.com>
* fix: truncation on usage selector Fixes the project selector truncation for selected value in the selector. * chore: move truncation to component itself * nit: prevent cehvron from shrinking * chore: tidy up
* feat: remove redundant sort by We had conflicting sort by dropdown which clashed with the individual column sorting itself. Either we do something similar to our table editor or leave it out for now. Opting to leave it out for now. * fix: alignment of download dropdown This aligns the download dropdown on the Query Performance page to look visually correct. * feat: improved query search This improves our query search in the Query Performance area. Now it does a local search through the available queries in the table. I removed it requesting the string from server for now. Simple :x q * fix: increased width of filter popover The roles filter popover is was too narrow for its contents. Increased teh size slightly. * chore: remove commented out component * chore: update placeholder for query filter * fix: leftover prop on query performance page * feat: reintroduce sql based query for search Bringing back a hybrid approach - seems to work fine but also returns items that are not in your visible queries. * feat: use debounce on search query * feat: use nuqs instead of next router for roles * Tiny optimization for debounced search to immediately run query if clearing input * Add clear search CTA * Remove client side searching * Revert changes in useIndexInvalidation --------- Co-authored-by: Joshen Lim <[email protected]>
* Check over MCP page * Update apps/docs/content/guides/getting-started/mcp.mdx Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update apps/docs/content/guides/getting-started/mcp.mdx Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Prettier --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Kevin Grüneberg <[email protected]>
Sitemap generation is failing when SDKs are disabled because it expects to find generated files for the disabled SDKs. Fix by filtering to only generate sitemap entries for enabled SDKs. Co-authored-by: Chris Chinchilla <[email protected]>
* fix: rewrite relative URLs when syncing to GitHub discussion Relative URLs back to supabse.com won't work in GitHub discussions, so rewrite them back to absolute URLs starting with https://supabase.com * fix: replace all supabase urls with relative urls * chore: add linting for relative urls * chore: bump linter version * Prettier --------- Co-authored-by: Chris Chinchilla <[email protected]>
There is a bug in the Table Editor mobile view: 1. Open the Table Editor in mobile. 2. Open a tab with a table. 3. Use the Table Editor Menu to switch schemas. This switches the schema in the URL and in local storage, but the Table Editor Menu closes immediately and you can't see the list of tables in the new schema to pick. 4. Open the Table Editor Menu again to pick a new table. The schema automatically flips back to the previous schema, and the Table Editor Menu only flickers open temporarily before closing again. There is no way to access the tables for your newly selected schema. The cause of the bug: There is a useEffect that triggers every time the Table Editor Menu is opened in mobile. (It technically has selectedTable?.schema in its dependency array, but since the menu unmounts and remounts on visibility toggle, the effect runs regardless of whether global selectedTable state has changed. That's also why desktop works fine, because the menu is continuously mounted in desktop view.) When the useEffect runs, it sets the schema to the schema of the currently selected table. Therefore, what actually happens: 1. Schema is set to `schema_a`. The currently selected table is `schema_a.table_a`. 2. User changes schema to `schema_b`. 3. User reopens Table Editor Menu. useEffect runs. Currently selected table is `schema_a.table_a`, so the schema automatically changes back to `schema_a`. Menu automatically closes. The fix: The actual behavior on desktop right now is probably what we want: - The selected table is only used to set the schema if no explicit schema is provided. - If an explicit schema is provided, the user probably chose it, so we allow the schema to not match the currently selected table. The table tabs update to include the table schema anyway if the schema changes, so it should be somewhat obvious that the schema of the menu and the selected table don't match. Therefore, the logic we want is `!!selectedTable?.schema && !selectedSchema`. Because of this change, we can also take it out of the useEffect, which means less circular logic. that Co-authored-by: Joshen Lim <[email protected]>
* Temp hide the vulnerable_postgres_version lint * Console log
* gs * mobile * use announcement badge * use chevron * adjust spacing * rm dot --------- Co-authored-by: Jonathan Summers-Muir <[email protected]>
Identified a misplaced new line carriage. This PR removes it.
Pages that are disabled in navigation/site rendering are still shown in llms.txt. This change filters those pages out of the llms.txt build as well. Co-authored-by: Chris Chinchilla <[email protected]>
Co-authored-by: Chris Chinchilla <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
9 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.3)
Can you help keep this open source service alive? 💖 Please sponsor : )