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

Worker identifier is spelled three ways across `cf workers` commands (`<worker-id>`, `--worker-id`, `--worker`)

Abierto
  • ¿Algo no está bien?
#345 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
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
72/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
node.js, typescript
Área
cli

Línea de trabajo

Start by running the cf workers secrets update, cf workers versions list, and cf workers deployments create examples to compare their accepted worker arguments. Locate the generated command definitions for the 7 commands using --worker-id and 14 using --worker, then check the command-generation and CLI tests. Done means every cf workers command accepts one consistent worker option, with existing options continuing to work as aliases for either a name or ID where supported.

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

Descripción

Summary of the issue

Commands under cf workers take the Worker in three different ways:

Command How the Worker is passed
cf workers get, cf workers delete positional <worker-id>
cf workers versions list / get / delete --worker-id (required flag)
cf workers deployments list / create, cf workers secrets list / update / … --worker (alias --script-name)

So the obvious sequence of rolling back after setting a secret uses three spellings:

cf workers secrets update API_KEY --worker my-worker --text …
cf workers versions list --worker-id my-worker
cf workers deployments create --worker my-worker --versions '[…]'

cf workers versions list --worker my-worker fails with Missing required argument: worker-id, and cf workers versions list my-worker fails the same way. The spelling follows each API's path parameter (worker_id vs script_name), which leaks into the CLI. The cf launch post names consistency across commands as a goal, mainly for agents.

In the beta.16 bundle, 7 generated commands define --worker-id and 14 define --worker. beta.18 is the same.

Expected behaviour

One spelling for "which Worker" across cf workers … (e.g. --worker everywhere, accepting a name or ID), with the others kept as aliases.

Version of cf used

1.0.0-beta.16

System information and package versions
cf 1.0.0-beta.16 (also checked in the beta.18 package source)
macOS 27.0 arm64, Node 26.8.2, npm 11.19.1
Lenguaje dominante
TypeScript
Estrellas
916
Forks
53
Merge medio
18 h 26 min
PR fusionados (30 d)
177

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.