Closed Ehsan-Tal closed 2 months ago
We just need to finalize the habits table and the view model ui state (nasty) and some other things.
I think we need to figure out what image picker would need of the item instead of waiting for the image picker !
Also, we should do this because the table version would only matter if we launch it, right ? Duh ?
Okay, next session after a break - figure out the image picker, change the entities, uncomment the transaction code.
Then we need to make type converters for date and one for complexity
I.e., this only needs one session to complete
CODE DOESN'T WORK - OOPS, I DID IT AGAIN.
Too many changes, not enough commits.
It's okay, we can cut and figure it out soon enough. and then commit and make sure we do so
It works - there were a few minor issues circling the bigger issue: weird dates. The datetime was parsed, formatted, reparsed, etc., at every communication point. Now we've changed it to all use Long? in Milliseconds with a lot of instant objects though it's all translated into millseconds, e.g., Instant.now().toEpochMilli()
It does mean the queries look weird, but I'm also find with it since looking weird is such a minor problem compared to refactoring all of that code again.
Finality V2
13
30
15
HabitDao (requires finalizing the date types in the table - take inspiration from currentStreakorigin, etc.)
Uncommenting