fix: exclude bucket type in response for storage-py < 0.12.1 #744
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?
bucket list endpoint response includes a bucket type property for all requests
What is the new behavior?
bucket type property is excluded for storage-py versions before 0.12.1
Additional context
The storage-py client library throws a fatal error if it receives unexpected properties in the bucket list response. The type property was added to the expected values in v0.12.1
Fix PR: supabase/storage-py#380
Fix Release: https://github.com/supabase/storage-py/releases/tag/v0.12.1