CommandCodeAI / CommandCodeAI/command-code

Allow deleting remote Taste packages from web (Studio) and CLI

Abierto
#568 0 comentarios 2 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Lenguaje dominante
Sin datos de lenguaje
Estrellas
4k
Forks
350
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

Feature Description

Holas.
There is currently no way to delete remote Taste packages (commandcode.ai/username/taste). I verified
this in two places:

  1. Web / Studio: The Taste tab in commandcode.ai/studio only lets you view, push, and pull profiles.
    Opening a remote package shows no "Delete", "Remove", or trash icon to delete it. The public view
    (/username/taste) is read-only.
  2. CLI: cmdc taste (equivalent to npx taste) only exposes push, pull, list, lint, open. There is no
    delete/rm subcommand or flag to remove a remote package.

Request: Add the ability to delete remote Taste packages in both channels:

  • In Studio: a delete button per package (on the package card and/or in the detail view).
  • In CLI: a subcommand like cmdc taste delete --remote (or rm) that removes the package from
    the remote registry.
Use Case

I have 2 old remote packages (waku-portafolio, michi-cards-final) and want to reduce them to
a single one (my global Taste). Today the only option is to overwrite with push --overwrite; I cannot
delete the remote I no longer use. This accumulates obsolete profiles and prevents keeping a single
clean remote.

Additional Context

Expected behavior:

  • In Command Code Studio (commandcode.ai/studio → Taste tab), each remote Taste package should have
    a delete/remove control (trash icon or "Delete" button) both on the package card and inside the
    package detail view, allowing the user to permanently remove a remote package.
    • The CLI should provide a delete subcommand, e.g. cmdc taste delete --remote (or rm),
      that removes a package from the remote registry (commandcode.ai/username/taste).
    • A user should be able to reduce their remote Taste packages to a single one (e.g. their global
      Taste) by deleting the obsolete ones.

Actual behavior:

  • Studio's Taste tab only supports viewing, pushing, and pulling profiles. Opening a remote package
    shows no delete/remove option — the public view (/username/taste) is read-only.
    • cmdc taste --help lists only push, pull, list, lint, open. There is no delete/rm subcommand or
      flag to remove a remote package.
    • cmdc taste list --remote lists remote packages but offers no way to delete them.
    • The only available action is cmdc taste push --all --remote --overwrite, which overwrites an
      existing package but cannot remove a remote package the user no longer wants (e.g. old
      waku-portafolio and michi-cards-final packages remain in the registry with no deletion path).

Steps to reproduce:

  1. cmdc taste list --remote → lists remote packages with no delete option.
  2. cmdc taste --help → no delete command listed.
  3. Studio → Taste → open a package → no delete option.
How important is this to you?

Important for my workflow

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

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.

Línea de trabajo

No se nombran archivos ni pruebas. Empieza siguiendo el punto de entrada de cmdc taste y la pestaña Studio Taste; después, sigue cómo list --remote lee los paquetes y cómo se renderizan las tarjetas de paquetes o las vistas de detalle. La tarea estará terminada cuando un usuario autenticado pueda eliminar un paquete remoto seleccionado a través de ambos canales y el paquete se haya eliminado de los listados remotos.

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

Evaluación

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

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.