Thorsten Böttger
Thorsten Böttger
I agree that this makes sense for simple linear graphs (workflows), like the one you described:  But what should happen if the state machine gets one more state, representing...
@hectorvs-gxg What do you mean with `#before_state` and `#after_state` methods?
You mean completely overriding the _AASM_ definitions from the super class and start from scratch?
That's not possible with _AASM_, I'm sorry.
@youroff Sorry for coming back to this so late. Yes, a pull request would be nice :+1:
@andrewroth Since _AASM_ version `4.3.0` this should be sufficient `AASM::StateMachine[MyClass] = {}`
It's an interesting thought to do transitions implicitly in the background, while just using common ActiveRecord setters and savers only. I have two concerns though. 1. choosing the first transition...
Closing this issue now. Thanks anyhow for the suggestion!
@johnnyshields I'm sure the implementation is straightforward and quickly done (including tests). But I'm still not supporting your request, since "guessing" or simply taking the first event to be found...
For now, _AASM_ only supports external event-based triggers. But the field of internal-state triggers is interesting as well (sort of: if attribute _x_ changed from _a_ to _b_, then trigger...