Mirror files follow their prompts through edits, renames and removal
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
调研方向
Read src/Prompuff.Application/Services/PromptService.cs first, then inspect src/Prompuff.Infrastructure/Persistence/LibraryChangeMonitor.cs and LibraryWatcher in src/Prompuff.App/ViewModels/ShellServices.cs to understand how saves and data_version changes are handled. Trace the mirror behavior for prompts and workflows, and review ROADMAP.md for the Recently deleted rule. Done means Git shows edits, renames and removals as single-file changes, the specified cases are tested, and a missing or read-only mirror does not prevent saving.
由索引模型根据 Issue 内容生成。
描述
Once the mirror folder exists (#37), each file has to follow its prompt, so that Git shows a saved change as an edit rather than as a new file.
What to do
- Saving a prompt rewrites its file. A metadata change, such as a favorite or tags, rewrites the frontmatter too, since it's in the file.
- A prompt keeps its file name when its title changes. Two prompts with the same title get distinct names.
- Moving a prompt to Recently deleted leaves its file alone, and removing it for good deletes the file, so a restore never has to bring a file back. Record this in ROADMAP.md.
- Workflows follow the same rules in
workflows/. - Changes from the CLI or another copy reach the mirror too. The app already notices them through
data_version. - A mirror folder that's gone or read-only doesn't stop a save. Prompuff says what happened, and that the library is safe.
Where to look
src/Prompuff.Application/Services/PromptService.cs: where saves, deletes and restores happensrc/Prompuff.Infrastructure/Persistence/LibraryChangeMonitor.csandLibraryWatcherinsrc/Prompuff.App/ViewModels/ShellServices.cs
Done when
- With the mirror under Git, an edit, a rename and a removal each show up in
git diffas that one change to that one file. - Tests cover renames, duplicate titles, Recently deleted, removing for good, and a missing folder.
- 主要语言
- C#
- 星标
- 0
- 派生
- 1
- 平均合并
- 1 小时 21 分钟
- 30 天内合并 PR
- 22
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
hazeliscoding/prompuff 的其他 Issue
-
enhancement
难度 2/5 1-3 小时 新手友好度 78/100
hazeliscoding/prompuff#34 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
hazeliscoding/prompuff#22 ·
维护者通常 1 天内回复
-
good first issue
难度 2/5 1-3 小时 新手友好度 90/100
hazeliscoding/prompuff#14 ·
维护者通常 1 天内回复
-
good first issue
难度 1/5 1-3 小时 新手友好度 92/100
hazeliscoding/prompuff#13 ·
维护者通常 1 天内回复
-
enhancement good first issue
难度 2/5 1-3 小时 新手友好度 88/100
hazeliscoding/prompuff#12 ·
维护者通常 1 天内回复
查看 hazeliscoding/prompuff 的全部 Issue
相似的 Issue
-
track:release
难度 2/5 1-3 小时 新手友好度 80/100
-
[Bug] [Go] Ack returns nil when the server answers with a non-OK status可能已有人在做 @leizhiyuan 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 84/100
apache/rocketmq-clients#1465 ·
维护者通常 2 天内回复
-
fix(testing): HeadlessTerminal disposes services synchronously可能已有人在做 @zidad 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 69/100
RazorConsole/RazorConsole#388 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
-
难度 2/5 1-3 小时 新手友好度 72/100
starlinghq/starling#209 ·
维护者通常 1 天内回复