todo.org

Todo

[X] rewrite readme as org

… or move to that one? b/c it’s already done?

project-wide

[X] improve test coverage

[ ] add to clojars

[ ] write a larger usage guide

[ ] readme refresh

It’s been a few years!

parsing/writing

[X] handle round-tripping items/item-lists better

multi-items/lists in property buckets have long been a complex issue for me. I’m not sure how common they are in general.

The current solution uses dynamic bindings for white listing properties to treat as lists, but I really don’t like that as a solution.

Lately I’m wondering if it can be treated as a single elem when there’s one, or many if there are already many - just react to the data. then have an explicit update list command when you don’t want to overwrite the value. Could even be passed in as a list to imply a concat.

[X] parse proper org-priority

[X] support scheduled/deadline

[X] support ‘closed’

[X] don’t add empty property buckets to every item

[X] support source blocks

[X] support images with files/names/captions

[ ] support logbooks

right now it seems to just throw out items with logbooks

[ ] support tables

analyzing/manipulating org items

[ ] expose walk api for reducing over the nested structure

agenda

[ ] provide first class agenda CRUD support

maybe via clomacs?

cli features

for help dealing with roam duplicate uuid errors (the errors are definitely my fault, but still annoying)

SKIP doctor task: uuid duplication auto-magic fixer

Work has begun here, and works in interactive mode. Sadly this is blocked by the update function mishandling some org cases - in it’s current state it can wipe data from files that get updated. More info is in the parsing/writing todos above.

SKIP doctor task: clean up broken org-links after refiling/moving docs