From 5530715c4d85679a1f265f435d44e8e9dfa56d1e Mon Sep 17 00:00:00 2001 From: Kyle Bowman Date: Sun, 26 Jan 2025 21:22:28 -0500 Subject: [PATCH] Update todo list. --- todo.md | 32 +++++++++++++++++++++----------- 1 file changed, 21 insertions(+), 11 deletions(-) diff --git a/todo.md b/todo.md index b3fab67..fbf2c20 100644 --- a/todo.md +++ b/todo.md @@ -1,16 +1,26 @@ # To Do -1. Probable bug: Entries with duplicate labels -2. Add tests for each branch in `handle_*` -3. Clean up `handle_*` implementations where possible. Can I push details down? -4. Add a ~generic~ filters to `nom entry` that lets you select an entry - by column value. Default to label. This should work for show and update. -5. By default `nom entry show` shows `viewed=False`. -6. Add a `--dry-run` option `nom entry update` that lets you preview changes. (Default?) -7. Replace hardcoded paths. Stash "active" lists in a dotfile somewhere. (XDG env) 8. Add a bash alias that does `nom entry show | cut -d '|' -f2 | xdg-open && nom entry update --viewed=True` -9. Determine rules for when an entry should be removed from entry list. Add to - `nom entry update`. +1. Proper tests. Add data to tests. Entrylist, for instance. Update tests + so it doesn't look in my default location. +2. Clean up `handle_*` implementations where possible. Can I push details + down? Can I better handle dispatching commands? Put args closer to dispatch. +3. Replace hardcoded paths. Stash "active" lists in a dotfile somewhere. + (XDG env) 8. Add a bash alias that does `nom entry show | cut -d '|' -f2 | xdg-open && nom entry update --viewed=True` +4. Determine rules for when an entry should be removed from entry list. Add + to `nom entry update`. 1. It is not included in any feed that the entry list is based on. 2. `viewed=True` 3. Prompt user for deletion? -10. Try to package, install, demo, and deploy. \ No newline at end of file +5. Try to package, install, demo, and deploy. + +# Quote from the "Reasoning" field of my project planning AI session + +> Lastly, the user wants the ability to add an article directly into the +article table without it having to be linked to a feed. This is interesting +because it breaks the typical flow where articles come from feeds. I'll +need to design how the CLI will handle this—perhaps a separate command or +an option when adding feeds that allows specifying just an article's details. + +I feel somewhat vindicated. This request is the difference between a feed +reader and a general purpose reading manager. And it's *exactly* why I +struggled with the inherent data structure. \ No newline at end of file -- 2.39.5