fix: remove empty transform struct when generating document URLs #6
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.
Problem
When generating signed URLs for documents, the transform field was being sent as an empty struct (%Transform{}). This caused the Supabase backend to attempt applying image transformations to documents. The backend expects transform to be nil when not used, especially for non-image files like documents.
Solution
Rationale
This fix ensures that the Supabase backend does not attempt to apply image transformations to documents, avoiding unnecessary errors. By conditionally including the transform field, the request is cleaner and more accurate. The solution is simple, maintains backward compatibility, and works seamlessly for both document and image URL generation.