5b660c3c1ca0a0ac5049d2f20628c15e3e8853cb
BREAKING CHANGE: BuildWorkingSet() now accepts []*Task instead of *Filter Problem: - Working set IDs were assigned based on database query order (unsorted) - Reports displayed tasks in sorted order (by urgency) - Result: IDs didn't match displayed task positions (ID 1 wasn't first task) Solution: - Changed BuildWorkingSet() to accept pre-sorted task slice - Reports now pass sorted tasks to BuildWorkingSet() - IDs are assigned sequentially to match display order (1, 2, 3...) Behavior: - Reports rebuild working set on every execution with fresh IDs - Task operations (done, modify, info) use saved working set IDs - After completing a task, re-running report renumbers remaining tasks Example: Before: opal list shows ID 1 = low urgency task (wrong) After: opal list shows ID 1 = highest urgency task (correct) Tested scenarios: ✓ List report: IDs 1-N match urgency order ✓ Next report: IDs 1-5 match top urgent tasks ✓ Task completion: IDs renumber correctly after removal ✓ Multiple operations: Use saved working set (correct behavior) ✓ Different reports: Each builds own sequential IDs
Notr
Simple Go application for organizing and referencing notes. Loosely based on Obsidian.
Implementation: See jade-depo/ directory for the CLI tool.
Workflow
I take notes in two primary ways:
Phone
- Quick notes, on the go.
- View and search notes.
Workstation
- Using NeoVim for notetaking
Other infrastructure
- I host a VPS with a Nextcloud and Gitea instances.
What I want
- A Obsidian Vault like structure. A folder where notes live.
- A file is a note
- Can also store attachments, such as images. These files can then be referenced in the relevant notes.
- Directories is the main organization method, although tags and links can seam-lesly cross directories boundries.
- Markdown syntax (this can be handled by NeoVim and a markdown editor on other devices.)
- Tags: Syntax +tag
- Note links for referencing other notes or any other vault files. Syntax uncertain. Obsidian uses ?
- See reports about the vault. Tag report
- At some point I would like to have a web-app and host it on my server. This would integrate with my authentik service for auth, and would be a live view of a users vault
- OCR would be great.
Implementation
I have a tendency to scope creep and never actually getting a usable product, so an important goal here is practicing getting a usable app up and running. This should not have to be the biggest project, so I'll try to predict the process:
Version 0.1
Here I use other tools for the note-taking and accept that any searching is on a directory basis only.
- I create a directory in Nextcloud. This I will start using immediately.
- Find a good Markdown editor for android.
- Adopt any crutial Obsidian notes
Version 1.0 ✓
This is where I can use Notr to find and search notes on my workstation. CLI implementation complete!
- Process notes. Metadata and diffs
- Search and Filter by tags
- Search and Filter by content
- Add, edit, delete notes
- List all notes and tags
Version 2.0
Here I can do the same on my phone.
Also:
- OCR
Metadata approach
Multiple approaches possible.
Description
Languages
Go
75.3%
Svelte
17.5%
JavaScript
5.3%
CSS
1.2%
HTML
0.4%
Other
0.3%