Skip to content

feat: Custom Board Dimensions #174

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

mmaciesowicz
Copy link

Feature Changes

  • Added customization to the board dimensions (allow the user to specify the number of rows and columns on the board) up to 16x16 boards.
  • Updated API: boardDimensions: object: {rows: 8, columns: 8 }
  • Created new Storybook entry to test

Why is this Useful?

There are thousands of chess variants that exist -- many of which do not use a standard board size of 8x8. For example, Capablanca Chess uses a 10×8 board, Double Chess requires a 16×12 board, and Los Alamos Chess is played on a 6×6 board. This gives users the flexibility to change the board to their own need while still maintaining compatibility with standard 8x8 board sizes.

How to Test

  • npm run storybook
  • Choose the 'Varying Board Dimensions' setting/option
    image

Dev Testing

react-chessboard-demo.mp4

Copy link

vercel bot commented Dec 5, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
react-chessboard ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 18, 2025 8:05pm

@Clariity
Copy link
Owner

v5 is now ready for beta testing, please install the latest beta to give it a try:

pnpm i react-chessboard@beta

You will need to follow the upgrade guide

this feature exists in the new version and can be found here in the new docs

@Clariity
Copy link
Owner

Clariity commented Jul 3, 2025

closing due to inactivity, please open a new PR if you find the issue within v5

@Clariity Clariity closed this Jul 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants