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 天内回复