lostdesign / lostdesign/linked
✨ add #tag function
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1k
- Forks
- 76
- PR merge metrics
- No merged PRs in 30d
Description
While the upcoming search may not need this, some may want to explicitly set their tags themselves. flexsearch does support tags and storing additional values would not hurt anyways.
Acceptance Criteria
- use tiptap in order to create a custom node when someone types a # followed by some text
- that new extension then should push the tag into the current day file
- flexsearch should be extended by the tags attribute, which is just
tagsitself, from there on, it would register the tags - deleting tags should remove them from the day file as well as the search index (maybe the later is automatic, to be tested)
- adding duplicates should not be possible
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Tiptap editor, current-day file persistence, and FlexSearch index setup in the Electron app. Trace how note content and indexed fields are updated, then implement the acceptance criteria: # tags become custom nodes, persist in the day file and tags index, are removed when deleted, and cannot be duplicated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, javascript
- Domain
- content, desktop, search
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100