You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@mivanov says: Currently can't select midnight as the end time. The best you can do right now is manually type in 11:59PM or something. With the current data model, we can't actually store midnight end time properly (it starts the day). We can either
make a hacky workaround where we help you enter 11:59 using the widget and then we render it as "midnight" or
change the model to store a start time and duration. queries will become less symmetric but we can support lots of varied scenarios
We can prob punt this, but also not that hard to fix.
From @philipn on December 30, 2012 1:43
@mivanov says: Currently can't select midnight as the end time. The best you can do right now is manually type in 11:59PM or something. With the current data model, we can't actually store midnight end time properly (it starts the day). We can either
make a hacky workaround where we help you enter 11:59 using the widget and then we render it as "midnight" or
change the model to store a start time and duration. queries will become less symmetric but we can support lots of varied scenarios
We can prob punt this, but also not that hard to fix.
Copied from original issue: localwiki/localwiki#420
The text was updated successfully, but these errors were encountered: