Storage class could use improved organization
Registered by
Jeremy Knope
There's a lot of messiness that could be cleaned up in the TwitterStorage class. Creating TTUser/TTTweet objects earlier on, possibly within MGTwitterEngine would provide for cleaner code, cleaner handling of changed-data like for User.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
(?)
