Refactor SimpleTaskInstance to prevent future TaskInstance field addition to lost during serialisation
Open
area:core
kind:feature
- Dominant language
- Python
- Stars
- 46.9k
- Forks
- 17.8k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 483
Description
Context: #16768
> Right now, if a field is added to `TaskInstance`, `SimpleTaskInstance` and `_execute_task_callbacks` needed to be checked to pass them on. This can be difficult to maintain.
Ideas are very much welcomed.
Contributor guide
Research direction
Start with TaskInstance, SimpleTaskInstance, and _execute_task_callbacks, then read the context from issue #16768. Determine a serialization approach that does not require manually updating these paths whenever TaskInstance gains a field; done means future TaskInstance fields are not lost during serialization.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, data-engineering
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100