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

feat(HttpClient): add span-customization hook

Cerrado
  • ¿Algo no está bien?
#8,053 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@ArjunCodess ya está trabajando en esto.

Desde el 19/9/2026.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
api, observability

Línea de trabajo

Start by locating the HttpClient tracing implementation and the existing span-name, whitelisted-header, and redacted-header customization points. Trace where the request, response, and client span are available, then clarify the hook's lifecycle and supported span changes; done means per-request customization covers the stated attributes, status, and kind requirements without replacing the client.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement
What is the problem this feature would solve?

The client span that HttpClient creates is almost entirely fixed. Today you can only customize the span name, whitelisted headers, and redacted headers.

So short of replacing the whole client, none of the following is possible per request:

  • Add attributes to just the client span. Effect.annotateSpans reaches it, but it propagates to every span created in scope, so the attribute also lands on nested spans. Effect.annotateCurrentSpan only touches the current span, but the client span is created inside the client call and is never the current span at your call site, so it can't reach it either.
  • Add http.route or another low-cardinality template attribute.
  • Override or redact url.full / url.query / url.path. Query strings and path segments are captured verbatim.
  • Set span status for non-2xx. HttpClient returns 4xx/5xx as a successful response, so the span carries a status_code attribute but no error status.
  • Change the span kind, for example a producer-style fire-and-forget.
What is the feature you are proposing to solve the problem?

A span-customization hook on HttpClient that receives the span along with the request (and the response when available) and can do anything to the span: set or overwrite any attribute (including the built-in url.* ones), add peer.service / http.route / arbitrary attributes, set span status, and set the span kind.

In addition to the hook, maybe we should also provide URL query redaction control, symmetric with CurrentRedactedNames for headers.

What alternatives have you considered?
  • Disable HttpClient's built-in tracing and instrument the calls by hand.
  • Collector-side processors. But it's out of process and the sensitive data leaves your app, so you're relying on the collector to prune it before it's stored or forwarded.
Lenguaje dominante
TypeScript
Estrellas
16.7k
Forks
808
Merge medio
10 h 33 min
PR fusionados (30 d)
830

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 Effect-TS/effect

Todos los issues de Effect-TS/effect

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.