Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scene should derive from Task #70

Closed
2 tasks done
eoyilmaz opened this issue Jun 9, 2022 · 0 comments · Fixed by #111
Closed
2 tasks done

Scene should derive from Task #70

eoyilmaz opened this issue Jun 9, 2022 · 0 comments · Fixed by #111
Assignees
Milestone

Comments

@eoyilmaz
Copy link
Owner

eoyilmaz commented Jun 9, 2022

User Story

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

  1. Derive the Scene class from Task.
  2. 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.

@eoyilmaz eoyilmaz self-assigned this Jun 9, 2022
@eoyilmaz eoyilmaz added this to the 1.0.0 milestone Dec 8, 2022
eoyilmaz added a commit that referenced this issue Nov 15, 2024
eoyilmaz added a commit that referenced this issue Nov 15, 2024
@eoyilmaz eoyilmaz linked a pull request Nov 15, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant