Updated example code for ownership owner_id in storage #28366
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
Corrected the example code in the documentation to reflect that `owner_id` is a text string, not a UUID. This update prevents errors caused by incorrect usage of `owner_id` as a UUID in examples.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
|
@acetrondi is attempting to deploy a commit to the Supabase Team on Vercel. A member of the Team first needs to authorize 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.
Corrected the example code in the documentation for storage in supabase
Corrected the example code in the documentation to reflect that owner_id is a text string, not a UUID. This update prevents errors caused by incorrect usage of owner_id as a UUID in examples.
I have read the CONTRIBUTING.md file.
YES
What kind of change does this PR introduce?
Docs update
What is the current behavior?
The current behavior in the documentation incorrectly suggests using owner_id as a UUID, leading to potential errors when users attempt to apply this in practice.
What is the new behavior?
The documentation now correctly reflects that owner_id is a text string, providing accurate guidance for users.
Additional context
This update ensures that developers who reference the documentation will no longer encounter errors related to incorrect data types when using owner_id in their projects.