search: index entry bodies (Notes and Evidence) with a lazily loaded prebuilt index
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 42/100
- Issue 類型
- 功能
- 描述清晰度
- 描述清楚
- 活躍度
- 活躍
- 技術堆疊
- javascript
- 領域
- search
研究方向
Start with site/lib/search.mjs, especially searchFields(e) and scoreFields, then check the build flow that produces dist/search-index.json and the existing search tests. Add a fixture whose Notes contain a unique word and verify it is found with body hits ranked below name and tag hits. Done when the index loads on first keystroke, the initial home page payload is unchanged, snippets appear for body matches, and the ROADMAP item moves to Done.
由索引模型根據 Issue 內容生成。
描述
Why it matters
Searching "GDPR", "share-alike", "Steam disclosure", "AGPL export" or "file conversion" finds nothing, although those phrases are exactly what the Notes sections record. The catalog's differentiator is the licence reading, and that text is unsearchable. ROADMAP.md lists full-text search as planned.
Evidence
site/lib/search.mjs:23-29searchFields(e)builds three fields (name/publisher/tags, summary, licence); body text is excluded.data.jsis already ~326 KB (see #75), so appending full bodies would roughly double it.
Suggested approach
- At build time tokenise each body (lowercase, stop words out, light stemming) and emit a compact inverted index
dist/search-index.json(token → entry ids), fetched on the first keystroke rather than on page load. - Score body hits below name/tag hits in
scoreFieldsso current ranking holds. - Show a one-line snippet around the match on the card when the hit came from the body.
- Test with a fixture entry whose Notes contain a unique word.
Done when
A word that only appears in an entry's Notes returns that entry, the home-page payload before the first search is unchanged, and the ROADMAP item moves to Done.
- 主要語言
- JavaScript
- 星號
- 58
- 分支
- 15
- 平均合併
- 16 小時 53 分鐘
- 30 天內合併 PR
- 14
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
TMHSDigital/Free-Game-Dev-Assets 的其他 Issue
-
community marketing priority: low
難度 2/5 1-3 小時 新手友好度 72/100
TMHSDigital/Free-Game-Dev-Assets#151 ·
維護者通常 1 天內回覆
-
documentation priority: medium
難度 2/5 1-3 小時 新手友好度 78/100
TMHSDigital/Free-Game-Dev-Assets#72 ·
維護者通常 1 天內回覆
-
enhancement
難度 1/5 1-3 小時 新手友好度 68/100
TMHSDigital/Free-Game-Dev-Assets#3 · 1 則留言 ·
維護者通常 1 天內回覆
-
marketing priority: low
難度 2/5 1-3 小時 新手友好度 55/100
TMHSDigital/Free-Game-Dev-Assets#152 ·
維護者通常 1 天內回覆
-
feature priority: medium
難度 5/5 一週以上 新手友好度 25/100
TMHSDigital/Free-Game-Dev-Assets#144 ·
維護者通常 1 天內回覆
查看 TMHSDigital/Free-Game-Dev-Assets 的全部 Issue
相似的 Issue
-
難度 1/5 1 小時以內 新手友好度 72/100
維護者通常 1 天內回覆
-
type/bug
難度 2/5 1-3 小時 新手友好度 62/100
flarum/framework#5301 · 1 則留言 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 82/100
AOSSIE-Org/BabyNest#284 ·
維護者通常 1 天內回覆
-
status:untriaged
難度 1/5 1 小時以內 新手友好度 86/100
midnightntwrk/servicedesk#275 ·
維護者通常 1 天內回覆
-
難度 1/5 1 小時以內 新手友好度 85/100
seek4science/seek#2762 ·
維護者通常 5 天內回覆