Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
#249 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@Tr00d ya está trabajando en esto.

Desde el 1/7/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

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

Lenguaje dominante
C#
Estrellas
700
Forks
105
Merge medio
1 d 21 h
PR fusionados (30 d)
41

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de supabase/supabase-csharp

Todos los issues de supabase/supabase-csharp

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.