Refactor action result processing (make it as a pipeline)
Registered by
Renat Akhmerov
Make action result processing pipeline more granular and clear. Now it’s hard to track how action result processing happens whereas it’s obviously a cascade processing when we have a chain of objects whose states are sequentially related: Object1 influences state of Object2, Object2 influences state of Object3. In our case Object1 - action execution, Object2 - task execution, Object3 - workflow execution. We need to reflect this pattern well in the code.
This will increase maintainability significantly.
Blueprint information
- Status:
- Complete
- Approver:
- Renat Akhmerov
- Priority:
- High
- Drafter:
- Renat Akhmerov
- Direction:
- Approved
- Assignee:
- Renat Akhmerov
- Definition:
- Approved
- Series goal:
- Accepted for newton
- Implementation:
- Implemented
- Milestone target:
- newton-1
- Started by
- Renat Akhmerov
- Completed by
- Renat Akhmerov
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
WIP: engine refactoring
Gerrit topic: https:/
(?)