AcademySoftwareFoundation / AcademySoftwareFoundation/OpenTimelineIO
Class hierarchy of Transition vs Item vs Composable not quite right.
Open
needs discussion
- Dominant language
- C++
- Stars
- 2k
- Forks
- 351
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 1
Description
There are a few methods, like `range_in_parent` that are implemented on Transition, but really belong to Item. Should Transition be an Item or should those methods move to Composable?
Contributor guide
Research direction
Review the Transition, Item, and Composable class definitions and the range_in_parent implementations mentioned in the issue. Determine the intended ownership and inheritance relationship, then confirm the agreed design with maintainers before changing it; done means the hierarchy and method placement are consistent without changing existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100