Mirror files follow their prompts through edits, renames and removal
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
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.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- C#
- Stars
- 0
- Forks
- 1
- Avg merge
- 1h 21m
- Merged PRs (30d)
- 22
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from hazeliscoding/prompuff
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
hazeliscoding/prompuff#34 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
hazeliscoding/prompuff#22 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
hazeliscoding/prompuff#14 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
hazeliscoding/prompuff#13 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
hazeliscoding/prompuff#12 ·
Maintainers usually reply within 1 day
All issues in hazeliscoding/prompuff
Similar issues
-
area-multitenancy area-security p1-recommended priority-high technical-debt
Difficulty 2/5 Under an hour Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
help wanted needs-unity ready for a contributor
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
eyalgolan/statecraft-israel#1542 ·
Maintainers usually reply within 1 day
-
kind/enhancement Provider Upgrade pulumi/pulumi-azure R1 Task
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
pulumi/pulumi-azure#3669 ·
-
type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day