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

Implement State Machine #344

Closed
toastercup opened this issue Sep 22, 2016 · 2 comments
Closed

Implement State Machine #344

toastercup opened this issue Sep 22, 2016 · 2 comments
Assignees

Comments

@toastercup
Copy link
Member

This Issue will hold our discussions re: what state engine we go with. It looks like there are two options: state_machine and aasm. The former was abandoned 4 years ago, but now has a fork with a decent amount of activity. The latter looks just as active and fleshed out- therefore, I'd like to go through a quick research phase where we suss out the value of each. I'll be doing some research, but please comment if you have any further insight.

@toastercup
Copy link
Member Author

@toastercup
Copy link
Member Author

This was completed as part of #341. transitions was the gem of choice.

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

2 participants