Closed nickholt-driver closed 7 years ago
Should I use protocols or a traditional class hierarchy for this?
This would require pretty extensive refactoring of UI and backend. Might not be feasible
I could use a different table section? One-offs wouldn't be check-marked or anything, and those could be swiped-to-delete.
This is probably pretty good
My current feeling is that this should not be done, ever. The purpose of the app is to track ROUTINE goals. This deviates from that and is bloat.
It would be nice to have the ability to enter just "one off" activities. These wouldn't factor into statistics, but it would be nice to see what all productive things I did on a day.
This would likely be a new entity, but think hard about how to model this.