Skip to content

feat(notes): a menu on each note in the tree to add inside, rename, move and delete - #412

Merged
adeelahmad merged 1 commit into
mainfrom
claude/project-thread-wm7xc9
Oct 15, 2026
Merged

adeelahmad merged 1 commit into
mainfrom
claude/project-thread-wm7xc9

Conversation

@adeelahmad

Copy link
Copy Markdown
Owner

Requested by Adeel · project thread

Description

Before: the notes tree in the left navigation showed about three rows under the links, below the fold on a phone. A note could only be moved by dragging it (which a phone can't do), and couldn't be renamed or deleted from the tree.

After: each row has a ⋯ menu (always visible on a touch screen) to add a note inside, rename it in place (Enter saves, Escape leaves it), move it (Move to… finds the note to put it in by name, Enter takes the first; Move to the top) and delete it with Undo. The navigation links and the tree scroll together, so a long tree gets the whole height.

How: components/notes/notes-tree.tsx gains the row menu, inline rename, a MoveTo dialog on the shared FindBox, and touch-visible row buttons ([@media(hover:none)]); components/app-shell/nav.tsx puts the links and the tree in one scroller. The existing POST /notes/{pid}/move, PATCH /notes/{pid} and DELETE /notes/{pid} (with Undo from #409) do the work; no API change.

Motivation and Context

Gap 6 of the notes UI audit (Adeel: "notes ui is very bad and is missing tons of things").

Steps to reproduce (if appropriate):

Notes tree → ⋯ on a note → Rename → type → Enter. ⋯ → Move to… → type part of another note's name → Enter. On a phone: open the navigation, the ⋯ shows on every row.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change; ! in the title)

Checklist:

  • The title is a Conventional Commit.
  • My code follows the code style of this project (make hooks checks it on commit).
  • I added or updated tests.
  • My change requires documentation updates, and I have updated docs/ accordingly.
  • Users need more than the title to understand it, so I wrote it under ## Unreleased in CHANGELOG.md.

Done questions (AGENTS.md)

  • Goal: notes can be added inside, renamed, moved and deleted from the tree, on a phone too; merged on green CI.
  • Agents: n/a, nothing new: the same moves, renames and deletes are POST /notes/{pid}/move, PATCH /notes/{pid} and DELETE /notes/{pid}, and the assistant's update_note moves notes.
  • Zero setup: nothing to install or configure.
  • Fewest clicks: rename is in place (Enter saves); Move to… is type and Enter; delete has Undo, no confirm.
  • Configurable: n/a, no new settings.
  • Light: no new dependency.
  • Private and secure: same access checks as before (editors change, viewers only open); no new surface.
  • Cost: no model calls.
  • User decides: nothing acts on its own; defaults unchanged.
  • Upgrades: nothing stored changes.
  • Honest: docs describe what is built.
  • Tests (__tests__/notes-tree.test.tsx: rename, move into, move to the top, add inside, delete with Undo) and docs (docs/notes.md, The tree) updated. Local: web 904 passed.
  • Open standards: n/a.
  • Refine later: keyboard moves (Alt+arrows) in the tree.

🤖 Generated with Claude Code

https://claude.ai/code/session_01RrY2byt5BHVeBXJUyfwWpb


Generated by Claude Code

…ove and delete

Each row of the notes tree has a ⋯ menu (always showing on a touch screen):
add a note inside, rename in place (Enter saves, Escape leaves it), Move to…
(find the note to put it in by name, never itself or a note inside it), Move
to the top, and Delete with Undo. The navigation links and the tree scroll
together, so a long tree has the whole height.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RrY2byt5BHVeBXJUyfwWpb
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants