Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

parity(storage): guard against empty transform routing through render endpoint [from supabase-js]

Open
#249 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@Tr00d is already working on this.

Since Jul 1, 2026.

Assessment

This issue has not been assessed yet.

Description

parity

SDK Parity: C# implementation needed

A bug fix was made in supabase-js that needs to be applied in supabase-community/storage-csharp for SDK parity.

Reference Implementation (supabase-js)

What Changed

Empty transform objects were treated as transform requests, routing through /render/image/ unnecessarily. The fix checks for actual properties before switching endpoints.

Current State in supabase-csharp

In StorageFileApi.cs, GetPublicUrl routes to /render/image/public/ and Download routes to /render/image/authenticated/ when transformOptions != null. A new TransformOptions() with no properties set still triggers the render endpoint.

Implementation Guidance

Add an emptiness check on TransformOptions before deciding the render path. For example, check if any transform properties (width, height, resize, format, quality) are non-default before routing to /render/image/.

Key Behaviors to Match
  • GetPublicUrl(path) without transform uses /object/ endpoint
  • GetPublicUrl(path, new TransformOptions()) with empty transform uses /object/ endpoint
  • GetPublicUrl(path, new TransformOptions { Width = 200 }) uses /render/image/
  • Same for Download()

Acceptance Criteria

  • Empty TransformOptions does not route through render endpoint
  • Actual transforms still route correctly
  • Unit tests
  • No breaking changes

Context

  • supabase-js version: v2.103.1+
  • Parity tracking: This issue was auto-generated by SDK parity analysis

Generated with Claude Code /sync-sdk-parity

Dominant language
C#
Stars
702
Forks
106
Avg merge
2d 21h
Merged PRs (30d)
51

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from supabase/supabase-csharp

All issues in supabase/supabase-csharp

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.