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

feat: Add next_state builtin change. #6

Merged
merged 1 commit into from
Sep 8, 2023
Merged

Conversation

jimsynz
Copy link
Contributor

@jimsynz jimsynz commented Sep 7, 2023

When there is only a single possible next state that can be transitioned into, we can automatically transition into that state.

Contributor checklist

  • Bug fixes include regression tests
  • Features include unit/acceptance tests

@jimsynz jimsynz requested a review from zachdaniel September 7, 2023 23:24
@jimsynz jimsynz self-assigned this Sep 7, 2023
@jimsynz
Copy link
Contributor Author

jimsynz commented Sep 7, 2023

This one's for you @sevenseacat, @StrongChris.

@zachdaniel
Copy link
Contributor

Just had a thought...could we just automatically do this? Then you don't even need to transition the state? Too magical?

When there is only a single possible next state that can be transitioned into, we can automatically transition into that state.
@jimsynz jimsynz force-pushed the feat/next-state-change branch from 552c21b to 6be9d15 Compare September 8, 2023 00:50
@sevenseacat
Copy link

Probably a little bit too magical for me. But this looks really good! ✨

@jimsynz jimsynz merged commit cf2bef0 into main Sep 8, 2023
12 checks passed
@jimsynz jimsynz deleted the feat/next-state-change branch September 8, 2023 01:35
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.

3 participants