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

Enable next option for setActivePlayers #450

Merged
merged 3 commits into from
Sep 10, 2019
Merged

Enable next option for setActivePlayers #450

merged 3 commits into from
Sep 10, 2019

Conversation

delucis
Copy link
Member

@delucis delucis commented Sep 9, 2019

Continuing work towards #445

This enables a next option for setActivePlayers/turn.activePlayers, including support for nested next options.

Currently still relies on `once` and will need refactoring once 
`moveLimit` replaces that.
Stores `next` and uses it to set `activePlayers` when `activePlayers`  
becomes empty. Supports nested `next` options.
@nicolodavis nicolodavis merged commit 0233c9b into boardgameio:phases-overhaul Sep 10, 2019
nicolodavis pushed a commit that referenced this pull request Sep 10, 2019
* test: Write test for `next` syntax when setting `activePlayers`

Currently still relies on `once` and will need refactoring once 
`moveLimit` replaces that.

* feat: Enable `next` option to `setActivePlayers`

Stores `next` and uses it to set `activePlayers` when `activePlayers`  
becomes empty. Supports nested `next` options.

* refactor: Tidy up variable names in `ProcessMove`
@delucis delucis deleted the delucis/feat/next-active-players branch September 10, 2019 23:13
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.

None yet

2 participants