Chore: update realtime functions to use fully qualified names #862
Conversation
This file contains 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 ↗︎ 1 Ignored Deployment
|
filipecabaco
force-pushed
the
feat-use-fully-qualified-names
branch
from
d82cf72 to
b34a6b0
Compare
|
@filipecabaco can you take a look? |
|
this needs to be redone on a new migration to tackle the changes we did for roles 👀 |
|
I can start over and make the changes again, in that case it might be worth closing this one and starting fresh :) |
|
sorry for not merging it at the right time 😞 lets do that if you are ok with it |
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.
What kind of change does this PR introduce?
Feat: use fully qualified names for most realtime functions. (no update on realtime.apply_rls) as I think that should be done through https://github.com/supabase/walrus. Everything else migrated to use fully qualified names.
Fixes this issue:
https://supabase.com/docs/guides/database/database-linter?queryGroups=lint&lint=0011_function_search_path_mutable
What is the current behavior?
Please link any relevant issues here.
What is the new behavior?
Feel free to include screenshots if it includes visual changes.
Additional context
Add any other context or screenshots.