Skip to content
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

Correct handling of ambigous moves #28

Open
portnov opened this issue Mar 10, 2019 · 0 comments
Open

Correct handling of ambigous moves #28

portnov opened this issue Mar 10, 2019 · 0 comments

Comments

@portnov
Copy link
Owner

portnov commented Mar 10, 2019

There are situations when specifying "source" and "destination" is not enough to unambiguously determine a move.
Such cases must be automatically detected at server side, and such fact must be reported to client;
Python client should enforce user to specify the move in "step-by-step" mode for such cases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant