Make lifecycles on STI subclasses work better
Reported by Matt Jones | August 10th, 2009 @ 11:11 AM | in Beyond Hobo 1.0
Currently, creator actions defined on an STI base class don't create objects of the subclasses, and the only workaround is to copy the lifecycle into the subclass model. At the very least, subclasses without an explicit lifecycle should work correctly, and preferably subclasses should be able to add states and transitions.
Comments and changes to this ticket
-
Tom Locke October 24th, 2009 @ 06:11 PM
- State changed from “new” to “open”
-
Matt Jones November 10th, 2009 @ 04:24 AM
- State changed from “open” to “investigating”
I think this is fixed now, but will investigate to make sure. The "adding states" part would be nice to have, though.
-
Matt Jones November 30th, 2009 @ 05:43 PM
- State changed from “investigating” to “open”
- Title changed from “Make lifecycles on STI subclasses behave” to “Make lifecycles on STI subclasses work better”
- Milestone changed from “Hobo 1.0 - Final” to “Beyond Hobo 1.0”
Lifecycles work on STI subclasses now, but have to be copied from the parent. Cleaning this up (so that, for instance, a subclass can be created via a parent lifecycle creator action) will take some serious re-plumbing. We'll also need a method for handling redefined and removed transitions and states.
Punting to "Beyond 1.0", as the current code works.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Betelgeuse
Matt Jones
Tom Locke