You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This seems quite verbose and prone to error upon changes since I'm explicitly mirroring state transitions defined above. Am I correct in my understanding? Is there a reason not to allow do: on the transition?
Actually, there's a nuance that I can capture with the desired syntax, that I haven't with the second syntax: only run process_superceded when [:has_next?, :ended?], so do I need to copy those conditions too? The unexpected behavior comes with the potential for :active => :expired without meeting those conditions.
The text was updated successfully, but these errors were encountered:
This is a potential enhancement if others like the idea, or we can close this. I'd rather not have the repetetive DSL, yet I'm not too motivated by the issue to dive in and write code to solve it.
It appears that I cannot specify
do:
on a transition definition such asIf that's the case, I'll have to copy a very similar block to create
after_transition
s. This appears to be the only way:This seems quite verbose and prone to error upon changes since I'm explicitly mirroring state transitions defined above. Am I correct in my understanding? Is there a reason not to allow
do:
on thetransition
?Actually, there's a nuance that I can capture with the desired syntax, that I haven't with the second syntax: only run
process_superceded
when[:has_next?, :ended?]
, so do I need to copy those conditions too? The unexpected behavior comes with the potential for:active => :expired
without meeting those conditions.The text was updated successfully, but these errors were encountered: