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

RFC: Safe partial-update behavior for PUT-only APIs

Abierto
  • ¿Algo no está bien?
#54 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
typescript
Área
api, backend-api-design, cli, testing-qa

Línea de trabajo

Start with the CLI update command and the GET, merge, then PUT flow described in the issue, then inspect endpoint schemas and available concurrency tokens. Resolve the safety policy before implementation; done means the supported policy is documented and eligible endpoints have concurrency and failure-path tests, including dry-run secret handling.

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

Descripción

enhancement priority: p2

Context

Some APIs expose replacement-oriented PUT operations but no PATCH operation. Users may still expect a CLI update command to preserve fields they did not specify.

A generic GET, merge, then PUT flow could emulate a partial update, but it can also overwrite concurrent changes or mishandle fields whose omission, null, empty value, or server default have different meanings.

Questions to resolve

  • Which endpoints have a concurrency token such as an ETag or version?
  • Can replacement schemas distinguish omitted fields from explicit clearing?
  • Which operations are idempotent and safe to retry?
  • How should secrets, write-only fields, computed fields, and server defaults be handled?
  • Should emulation be opt-in, endpoint-specific, or rejected when safety cannot be proven?

Safety requirements

  • Do not perform an unguarded read-modify-write when concurrent changes can be lost.
  • Preserve explicit clearing and replacement semantics.
  • Fail before mutation when the current representation cannot be reconstructed safely.
  • Show the effective request through dry-run without exposing secrets.

Outcome

Document the supported policy and implement it only for endpoints that satisfy the agreed safety constraints, with concurrency and failure-path tests.

Lenguaje dominante
TypeScript
Estrellas
960
Forks
62
Merge medio
23 h 46 min
PR fusionados (30 d)
217

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 cloudflare/cf

Todos los issues de cloudflare/cf

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.