Logbook objects, not collections
It is proposed to stop treating logbook object as collection of smaller objects: LogBook and FlowDetails should be made simple data-transfer objects, not containers for FlowDetails and AtomDetails respectively. Corresponding API should be moved to backends.
Blueprint information
- Status:
- Started
- Approver:
- Joshua Harlow
- Priority:
- High
- Drafter:
- Ivan Melnikov
- Direction:
- Needs approval
- Assignee:
- Joshua Harlow
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Slow progress
- Milestone target:
- None
- Started by
- Joshua Harlow
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Can u explain this in more depth, still unsure what it would mean. Thanks!
I tried to explain what I mean on wiki: https:/
Thanks, I think I get it.
Gerrit topic: https:/
Updating milestone and approval settings prior to kilo. - dhellmann
Addressed by: https:/
Initial shift to having backends provide storage impls
Addressed by: https:/
If not provided create and populate a in-memory backend
Addressed by: https:/
Optionally do caching/updating of flowdetail in storage
