Repository navigation
B89: search past trails by what you remember - #67
Merged
Merged
Conversation
The CommandBar and the canvas search bar list up to four matches from all
trails under "In your trails", with why each matched, the day and the
trail. Local rules read words, times ("last Tuesday", "in October"), order
("after the Discogs page"), kinds ("video", "question") and a trail name.
Picking a result switches to its trail and selects its card, or marks its
row in the timeline when it never became a card.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011V7Bv7WZ9Q92MZoNWYwevQ
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
B89. Search past trails by what you remember.
Where (your choices: CommandBar + canvas search, local rules, go to it in its trail)
after “Memex – Encyclopedia” · Tue 3 Nov · Reading list.What NODE reads (own rules, no AI, nothing leaves the computer)
Picking a result
Code
core/recall.js(no platform imports):parseRecall,recallIndex,recall.main.js:trail:recall.preload.js:trailRecall.renderer/app.js: CommandBar group,goRecall, timeline row marking.renderer/canvas.js: the list rows,showFound,flashCard.styles.css: tokens only.Not in this PR: the Chromium build (its canvas page has the hook but no data yet).
Tests
test/recall-demo.js(npm run test:recall, intest:unit): 9 checks, including 6,000 pages in 40 trails indexed and searched in about 30 ms.test/e2e/51-trail-recall.js(13 checks), in both CI e2e lists.test:unit, and e2e 33, 34, 36, 42, 43, 44, 49 and 50 still pass.Generated by Claude Code