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
As a developer using the Stalker library I want the Scene class to be deriving from the Task class so that it is possible ot use it in Task hierarchies along with Asset, Shot and Sequence.
Acceptance Criteria
Derive the Scene class from Task.
Add Alembic migration script for this change.
Original Description
The data that Scene entity is representing is commonly required in project hierarchies. But in the current implementation the Scene can not be directly used in Task hierarchies because it is not deriving from the Task and generally a Task with the type attribute is set to a Type object with the name attribute value of Scene is used and because we have a Scene class it creates a clutter.
The text was updated successfully, but these errors were encountered:
User Story
As a developer using the Stalker library I want the
Scene
class to be deriving from theTask
class so that it is possible ot use it inTask
hierarchies along withAsset
,Shot
andSequence
.Acceptance Criteria
Scene
class fromTask
.Original Description
The data that
Scene
entity is representing is commonly required in project hierarchies. But in the current implementation theScene
can not be directly used inTask
hierarchies because it is not deriving from theTask
and generally aTask
with thetype
attribute is set to aType
object with thename
attribute value ofScene
is used and because we have aScene
class it creates a clutter.The text was updated successfully, but these errors were encountered: