CommandCodeAI / CommandCodeAI/command-code

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

未關閉
#568 0 則留言 2 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

主要語言
沒有語言資料
星號
4k
分支
350
PR 合併指標
30 天內沒有已合併 PR

描述

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

貢獻指南

這個儲存庫沒有索引到貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

研究方向

未指定檔案或測試。先追蹤 cmdc taste 進入點和 Studio Taste 分頁,然後了解 list --remote 如何讀取套件,以及套件卡片或詳細檢視如何呈現。完成標準是:已驗證的使用者可以透過兩個管道刪除選取的遠端套件,且該套件已從遠端清單中移除。

由索引模型根據 Issue 內容生成。

評估

技術堆疊
cli
領域
cli, web-dev
Issue 類型
功能
難度
4/5
預估耗時
3-5 天
活躍度
冷清
描述清晰度
基本清楚
新手友好度
48/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。