Unify product Clone, "Save as new" and admin "Save as new" into a single clone feature
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start by tracing ProductCloneForm and the UI clone view and API clone action; compare their behavior with ProductForm and ProductAdmin.save_model. Identify how clone options handle copied data, then follow the existing paths for vulnerability analyses and codebase resource deployment links. Done means Clone is the sole duplication path and includes those data, while the two “Save as new” actions are removed.
由索引模型根据 Issue 内容生成。
描述
Following:
A product can be duplicated in 3 different ways, each with its own implementation:
- Clone:
ProductCloneForm, used by the UI clone view and the APIcloneaction - Save as new:
ProductForm, on the product edit page - Admin:
ProductAdmin.save_model, the "Save as new" button in the admin
They do not copy the same data, so the result depends on which one is used:
| Data | Clone | Save as new | Admin |
|---|---|---|---|
| Components, Packages, triage rulesets | Yes | Yes | Yes |
| Dependencies | Yes | No | No |
| Codebase resources | Yes | Yes | No |
Codebase resources deployment links (deployed_to) |
No | No | No |
| Vulnerability analyses | No | No | No |
| Object permissions | Optional | No | No |
| Triage re-evaluation | Yes | No | Yes |
The goal of a clone is to get the exact same product under a new version, except for the data unchecked in the clone options.
Proposed solution
- Keep Clone as the single way to duplicate a product, since the UI and the API already share it and it has the most complete behavior.
- Remove "Save as new" from the product edit form and from the product admin.
- Add the missing data to Clone: vulnerability analyses and codebase resources deployment links.
- 主要语言
- Python
- 星标
- 52
- 派生
- 30
- 平均合并
- 4 小时 57 分钟
- 30 天内合并 PR
- 21
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
aboutcode-org/dejacode 的其他 Issue
-
DOC: Document workflow between ScanCode.io and DejaCode可能已有人在做 @tdruez 于 1 天前认领。 未关闭documentation
难度 3/5 1-2 天 新手友好度 55/100
aboutcode-org/dejacode#606 · 2 条评论 ·
维护者通常 1 天内回复
-
design needed enhancement
难度 3/5 1-2 天 新手友好度 62/100
aboutcode-org/dejacode#561 · 3 条评论 ·
维护者通常 1 天内回复
-
Enhancement request: Refine License Category - Copyleft Limited可能重新可做 @hesa 于 119 天前认领，目前没有进行中的 PR。 未关闭design needed enhancement
aboutcode-org/dejacode#499 · 13 条评论 · 已指派 3 人 ·
维护者通常 1 天内回复
-
BUG: Product overview page splits product with many versions across pages可能重新可做 关联的 PR 已关闭且未合并。 未关闭bug design needed enhancement
难度 3/5 1-2 天 新手友好度 45/100
aboutcode-org/dejacode#460 ·
维护者通常 1 天内回复
-
design needed
难度 5/5 一周以上 新手友好度 20/100
aboutcode-org/dejacode#452 · 2 条评论 ·
维护者通常 1 天内回复
查看 aboutcode-org/dejacode 的全部 Issue
相似的 Issue
-
bug
难度 1/5 1 小时以内 新手友好度 86/100
awslabs/visual-asset-management-system#937 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
-
follow-up
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 83/100
维护者通常 3 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 2 天内回复