Show the opening name during play and in PGN export
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 58/100
- Issue 類型
- 功能
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- javascript
- 領域
- full-stack
研究方向
Start with js/notation.js for PGN export and js/game.js for the status display, then check index.html and sw.js for the UI and offline cache. Choose a licensed opening data source and match the played moves to its entries. Done when the longest match appears under the status line, persists after reload, is exported as ECO and Opening tags, and works offline.
由索引模型根據 Issue 內容生成。
描述
Summary
Show the name of the opening being played, for example "Ruy Lopez", under the status line. Also write it into PGN exports as ECO and Opening tags.
Where
js/notation.js(PGN export; there is no opening data today)index.html(status area)sw.js(APP_FILES, the offline cache list)
Details
No opening data or label exists anywhere in the code. In js/, "opening" only appears in a comment in js/notation.js.
Impact
This is a cheap learning aid for casual players. It also gives context to the Past games list and to exported PGN.
Suggested fix
- Bundle a small ECO table (a few hundred lines keyed by SAN move sequence or FEN) as a static file.
- Add the file to
APP_FILESinsw.jsso it works offline. - Show the longest matching name under the status line.
- Write
ECOandOpeningtags in PGN export.
Open questions:
- Which source to use, and its license. The lichess
chess-openingsdataset is CC0. - Whether to keep showing the last matched name after the game leaves the book.
Acceptance criteria
- 1.e4 e5 2.Nf3 Nc6 3.Bb5 shows "Ruy Lopez" (or the table's name for it).
- The name survives a reload and appears in the downloaded PGN.
- It works offline.
Getting started
- Relevant files:
js/notation.js,js/game.js(status),index.html,sw.js - How to run tests:
npm test
Filed by repo-audit/full-audit at 01c6a35. Severity: low. Effort: S. audit-key: enhancement|js/notation.js|opening-name
- 主要語言
- JavaScript
- 星號
- 4
- 分支
- 2
- 平均合併
- 22 小時 16 分鐘
- 30 天內合併 PR
- 9
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
TMHSDigital/Static_Chess 的其他 Issue
-
enhancement help wanted severity: low
難度 4/5 3-5 天 新手友好度 55/100
TMHSDigital/Static_Chess#184 ·
維護者通常 1 天內回覆
-
help wanted severity: medium tech-debt
難度 4/5 3-5 天 新手友好度 45/100
TMHSDigital/Static_Chess#173 ·
維護者通常 1 天內回覆
-
severity: medium tech-debt
難度 5/5 一週以上 新手友好度 35/100
TMHSDigital/Static_Chess#171 ·
維護者通常 1 天內回覆
-
help wanted performance severity: medium
難度 5/5 一週以上 新手友好度 38/100
TMHSDigital/Static_Chess#168 · 1 則留言 ·
維護者通常 1 天內回覆
-
enhancement help wanted severity: low
難度 4/5 3-5 天 新手友好度 61/100
TMHSDigital/Static_Chess#161 ·
維護者通常 1 天內回覆
查看 TMHSDigital/Static_Chess 的全部 Issue
相似的 Issue
-
priority: low server testing
難度 1/5 1 小時以內 新手友好度 88/100
blamechris/chroxy#9277 ·
維護者通常 1 天內回覆
-
[MCP]: page snapshots in .playwright-mcp/ are not git-ignored (.playwright-cli/ is, since #42318)未關閉
難度 2/5 1-3 小時 新手友好度 62/100
microsoft/playwright#44289 ·
維護者通常 1 天內回覆
-
Bug
難度 2/5 1-3 小時 新手友好度 75/100
Ionaru/easy-markdown-editor#657 ·
-
難度 2/5 1-3 小時 新手友好度 66/100
TMHSDigital/Free-Game-Dev-Assets#320 ·
維護者通常 1 天內回覆
-
area:webapp bug finding
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆