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

parity(supabase): propagate custom HttpClient to realtime client [from supabase-js]

Abierto
#247 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 this repository for SDK parity.

Reference Implementation (supabase-js)

What Changed

Custom fetch/HTTP client provided in SupabaseClient options was not being passed to the RealtimeClient.

Current State in supabase-csharp

SupabaseOptions has a Headers dictionary that is propagated to Realtime (since v1.1.1), but there is no HttpClient field. The Realtime ClientOptions also has no HttpClient property. A user who wants to use a custom HttpClient (for proxy, certificate pinning, custom handlers) cannot pass it to the Realtime client.

Implementation Guidance

Expected Fix

Add an HttpClient or HttpClientHandler property to SupabaseOptions and forward it to all sub-clients including Realtime. This ensures consistent HTTP behavior across all modules.

Key Behaviors to Match
  • Custom HttpClient set on SupabaseClient available to Realtime
  • Consistent with how other sub-clients handle HTTP configuration

Acceptance Criteria

  • HttpClient propagation mechanism added
  • Realtime client uses the shared HttpClient
  • Unit test verifying propagation
  • No breaking changes

Context

  • supabase-js version: v2.104.0+
  • 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.