* Update table editor tab labels when entering table editor if labels dont match entity names
* Update sqlEditorTabsCleanup to also update tab labels if they dont match snippet names
* Update table editor tabs clean up logic to be consistent with sql editgor
* Clean up
* Fix query block not showing labels
* Readd the css file for react-resizable.
* Add react-resizable package to resolve a style.css file not found issue
---------
Co-authored-by: Ivan Vasilov <vasilov.ivan@gmail.com>
* Use Context for Storage Explorer valtio store + shift views to new store
* Shift downloadFile from mobx store to utils
* Shift formatTime outside of StorageExplorerStore to StorageExplroer.utils
* Clean up
* Address comments
* Set up create trigger
* Hook up update trigger
* Deprecate CreateTrigger
* Small clean up DeleteTrigger
* Update apps/studio/components/interfaces/Database/Triggers/TriggerSheet.tsx
Co-authored-by: Alaister Young <alaister@users.noreply.github.com>
---------
Co-authored-by: Alaister Young <alaister@users.noreply.github.com>
- The docs explain "If you want the data returned as `text`, use the `->>` operator."
- Only the SQL example shows this using the `description` field
- All language should use `->>` for the description field
There were two bugs when trying to run the integrations page locally
with NEXT_PUBLIC_IS_PLATFORM=false:
1. The IS_PLATFORM check imported from common was not evaluating
correctly to a boolean. This is because I slapped a 'use client' on the
entire common package last year -_-""" which caused all its imports to
be evaluated to functions when used in server components. I have now
moved the 'use client's down to the submodules that actually need it.
2. When the integrations submenu is empty, the navigation menu errors
out because it expects all navigation items to either have children or
have links. Have updated this to gracefully hide empty headers.
* Remove leftover resizable group which weren't interactive.
* Put the input focus in a setTimeout.
* Alternative solution
* Small fix
* Bump threshold to 400ms
* Final fix, hopefully.
---------
Co-authored-by: Joshen Lim <joshenlimek@gmail.com>
Before:
The docs lint action doesn't run properly on forks because it tries to
use the branch name to identify the PR for updating, but the branch name is adapted on forks, so it is not `branch-name`, but `forking-account:branch-name`.
After:
Use the PR number instead to identify the PR instead.
* Disable the convertSqlToSupabaseJs tool because it relies on sql-to-rest which expects binaries of libpg-query.
* Comment out the code instead of deleting it.
* add filter bar component
* update filter bar demo
* add custom component support
* filter bar component
* example filter bar in use
* remove search filter
* reinstate older filter bar
* revert
* update registry
* update example name
* clean up example imports
* Update FilterBar.tsx
---------
Co-authored-by: Jonathan Summers-Muir <MildTomato@users.noreply.github.com>
* Don't build libpg-query package.
* Use the WASM build of libpg-query in ai-commands.
* Fix missing mdast type.
* fix: wasm loading in ai-commands tests
* fix: better polyfill
* Make the sql-to-rest page to be client-side only.
---------
Co-authored-by: Greg Richardson <greg.nmr@gmail.com>
An experiment in lowering docs preview build times. Build times have gotten quite long again (~12 minutes) because we are generating types on code blocks during prerendering. This wastes compute time building a lot of pages on preview branches that never get viewed, and slows down iteration speed.
Instead, let's only prerender on prod, and build on-demand for preview sites.
Limiting to realtime section for now to monitor the effects of changes.
Before:
Revalidation was turned off entirely for wrappers pages, and done daily for GraphQL pages.
After:
Revalidation is via tag. There is an /api/revalidate endpoint that is used by GitHub Actions on the federated repos to trigger the revalidation. This decreases the number of unnecessary page generations by Vercel, and gives the maintainers of federated repos more fine-grained control over when to reploy their docs (see the docs deployment playbook for more info).
Francesco Sansalvadore