Jake Gordon
Jake Gordon
Good question, I'll have to think about it. I'm not sure what the mechanism would be for forwarding the resolved/rejected value back to the user. Perhaps just storing it ephemerally...
Both of these issues should be fixed in v3 branch (shortly to be released to npm as v3.0.1). Any async lifecycle event that is rejected will now throw an exception...
Unfortunately (in both v2 and v3) the on**** handlers are intended for observing and performing side-effects and are not intended to change the fundamental nature of the current transition. Therefore...
Also consider the title of this issue "Trying to fire an event from a state" - I think this is a sign that my terminology is causing some confusion. The...
I've switched to minitest in the latest version (1.7) - is this still an issue?
Looks like different version of ImageMagick is causing a tiny variance in the generated image, The assert_equal in assert_reference_image should probably be changed to an assert_in_delta to handle tiny variations...
Is images/signup a normal directory? and what OS are you running on?
Can you share the code you used to construct the StateMachine?
This is fixed on the v3 branch (and in upcoming v3.0.1 release). All life cycle event observer methods use camel case, including when state or transition has an ALL_UPPERCASE name.
Yes, nested/composable states are a good idea, and a frequent request. I have (vague) plans on doing a fresh 3.0 version later this summer and nested states will be high...