Roadmap: chess.js 1.0.0See original GitHub issue
After 13 years of pre-1.0.0 development … it’s time.
This is a working document to track planned features/changes and their statuses for version 1.0.0. Please comment if there’s something you’d like to see included or changed. I appreciate and value your feedback. Check back frequently for updates.
I’ll push a basic typescript implementation to dev branch to use as starting point.
Please wait for the dev branch before submitting PR’s.
dev branch is now active
Proposed 1.0.0 Changes
- Rewrite library in typescript
- Use camelcase for API and everything else
- enforce with eslint rule
- Use exceptions in error states instead of returning
null. This will allow the library to provide more detailed error messages for common issues (e.g. bad moves, bad FEN, bad PGN). The functions that throw exceptions are listed in the API Changes section.
- Switch to using the sloppy FEN/PGN parser by default. The phrase sloppy is kind of passive aggressive, so maybe use the terms
loadin permissive mode (the default mode) should let the user load FEN without supplying castling rights, ep square, and move numbers (e.g. chess.load(
loadPgnshould allow an option to use the strict parser (is this even needed)???
moves()should work even if there are no kings on the board.
- Only set the en passant square when the opponent can legally make an en passant move. (see #294)
- Add a ‘lan’ (better name or is this ok??) property for long algebraic notation (see #259)
- Improve FEN validation. It should detect common hand-entered such as missing kings and incorrect castling rights.
- Use fast-check for property-based testing
- create a chess.js logo (maybe this is something the community can vote on??)
- Move documentation to chessjs.org
- Add an FAQ section to answer common questions
- Github issue template ensuring the reporter know the rules of chess before filing a bug (en passant gets flagged as a bug a few times a year)
- Prefer stackoverflow for chess.js usage questions, github issues for bugs
- The following functions should throw exceptions in the event of an error
Should acronyms be capitalized in function names (e.g.Decided not to capitalize acronyns.
loadPGN)? Consider the impact this could have on the
.pgn()functions. I’m leaning towards no, but it’s up for discussion.
- Should we adopt the chess.js TypeScript definitions from DefinitelyTyped as a basis for our types?
Future Changes beyond 1.0.0
- use piece lists for increased move generation performance
- use a parser generator to parse PGN
- add support for RAV (recursive annotation variations)
- add support for null moves
- chess960 support
Issues for First Time Contributors
- add a default separator=‘\n’ parameter to the
- Created a year ago
- Comments:15 (7 by maintainers)
Top GitHub Comments
Just began using this repo, but this is exciting! I’ll happily make some contributions once the FIX_ME branch is live.
Never use all caps for abbv. / acronyms, they tend to mess with other things.