Feat/assistant additions #30647
Merged
Feat/assistant additions #30647
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
5 Skipped Deployments
|
|
No changes detected in Preview Branches by Supabase. |
joshenlim
approved these changes
Nov 26, 2024
There was a problem hiding this comment.
LGTM - tested on preview
- Suggestions when editing policy with assistant
- schema and table gets passed to generate-v3 when querying on table editor
- table is not passed if on a page that also has ID param (e.g sql editor)
- Current SQL snippet gets passed as context when opening assistant in SQL editor
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I have read the CONTRIBUTING.md file.
YES
What kind of change does this PR introduce?
Makes some improvements to the assistant
there’s a bit here where the “Thinking…” loading state goes away too early and I think the request has failed
Show Query” when hidden, “Hide Query” when shown
border accidentally too short
Passes the current table and schema as context if we have it
Added "suggestions" when editing a policy