fix: revert setup instructions to supabase-dbdev#190
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
b3a3045 to
0fc11ec
Compare
imor
approved these changes
May 29, 2024
This was referenced May 29, 2024
Closed
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What kind of change does this PR introduce?
Bug fix
What is the current behavior?
Docs reference creating extensions with
@, e.g.supabase@dbdev, even though those changes haven't been rolled out yet and don't work when run against even a new Supabase project.What is the new behavior?
Revert back to the old way that still works and is still referenced here: https://database.dev/supabase/dbdev