Drafta 1.1.1: nested tags
Translated automatically from RussianRead the original →
In Drafta 1.1.1, a parent/child tag became a single tag, a tag tree appeared in the sidebar, and tags no longer move notes between notebooks.
In 1.1.1 tags with a slash became a full-fledged hierarchy. Previously, such a tag did not do what you expected of it.
How it was
A tag of the form #drafta/blog was split into two parts. Everything before the slash was considered the path to a notebook: when saving, the note silently moved to a notebook with that name, and if it did not exist, it was created. Only the last part, blog, remained as the tag. That is how I ended up with an extra “Drafta” notebook next to the real one.
How it is now
- One tag.
#drafta/blogis stored in full, and in the interface it is displayed asdrafta › blog. - Tree in the sidebar. Branches collapse just like notebooks. Clicking
draftashows notes with it and with all its subtags, and the counter counts them together. - Tags do not move notes. The notebook is set only explicitly.
- Renaming a branch.
drafta→workturns#drafta/bloginto#work/blogin all notes. Code in blocks and inline code is not touched, and an open note immediately shows the new text. - Colors are carried over from old tag names to nested ones.
- The MCP server understands the hierarchy: a filter by
draftaalso finds subtags,blogfindsdrafta/blog,list_tagsshows the tree with counters.
Fixed
Drafta could crash if you pinned or deleted a note by swiping on a list row: the list rearranged the row while the swipe animation was in progress. Now the action is performed after the swipe closes.