• The backend part includes a new field for Planner (cooking_date) with type DateTime without timezone and discarded the day field. If the API receives day though from older apps, it will be transformed into cooking_date.
• Before, missing values were modelled as -1. Now, at least in python, there is a datetime.min value which is 01st of January in the year 1.
• All datetime-objects are dates only and hence without time currently. To make comparing to datetime.now() theoretically more easy, the time is always set to 23:59:59. In the future, time could be used to differ between breakfast, lunch, etc.

TODO

• data migration (failed)
• handle date-times in the past: For example a user picks tomorrow as planned date but doesn't cook the recipe for two days. To sync with the day-logic, old recipes could be reset to the future by adding +7 days.
• squash commits