-
-
Notifications
You must be signed in to change notification settings - Fork 259
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
Exception starting from 7.8.0 #148
Comments
can you reproduce that issue with chessground alone? |
Yes. If you unzip the attached folder and open If i send the movable object as a map instead of an object, the exception goes away. If that is the expectation from clients going forward, you can close this bug and Although in that case, I don't think it should have been part of a minor version update. |
clients need to use |
For anyone with breaking changes, here is an example of how to do it now: https://github.com/ornicar/chessground-examples/blob/28ceac2c878c0187b5ad69aa68c5e25eba9f71ff/src/util.ts#L4 |
I am using the react-chessground component instead of using
chessground
directly so I have also filed this issue with them, but pretty sure it is caused by this checkinc190c18#diff-a2fcebf1963fad0da40a844a8d67da83R48
This exception started happening with version
7.8.0
ofchessground
. For a temporary fix, I have hardcoded my yarn.lock file to versionchessground@7.7.2
.Thanks.
The text was updated successfully, but these errors were encountered: