Add repeatable Tauri runtime verification for KG search and editor autocomplete
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- rust, tauri
- Domain
- desktop, testing-qa
Research direction
Start by locating the Tauri desktop startup path and the existing web proof path in a clean checkout. Build or package the debug app, then verify bundled defaults/resources and exercise search, search_kg_terms, find_documents_for_kg_term, and get_autocomplete_suggestions. Done means the repeatable verification path documents successful KG search and autocomplete checks and distinguishes packaging/resource failures from frontend failures.
Written by the indexing model from the issue text.
Description
Problem
The desktop app now builds, but packaged/runtime verification for Tauri mode is still lighter than the web proof path. The app needs explicit regression coverage that exercises bundled resources and Tauri commands, not only the Vite web flow.
Goal
Add a repeatable packaged/debug Tauri verification path for knowledge graph search and editor autocomplete.
Scope
- validate app startup with bundled defaults/resources
- exercise Tauri
search,search_kg_terms,find_documents_for_kg_term, andget_autocomplete_suggestions - add a regression script or automated test for the packaged/debug desktop path
- document manual fallback steps if full browser automation remains impractical
Acceptance
- Tauri desktop flow is documented and reproducible from a clean checkout
- KG search and article editor autocomplete are verified in Tauri mode
- failures clearly separate packaging/resource issues from frontend issues
- Dominant language
- Rust
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
More from terraphim/terraphim-ai-desktop
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
terraphim/terraphim-ai-desktop#20 · 1 comment ·
All issues in terraphim/terraphim-ai-desktop
Similar issues
-
risk:low runtime status:in-progress type:test
Difficulty 1/5 Under an hour Newbie friendliness 92/100
zeroclaw-labs/zeroclaw#11023 ·
-
good first issue refactor
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·