| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
For now we just hardcode that the local timezone of the site is UTC+2.
Good enough for now, but something that should be configurable.
Also split the date and time entries in the form again, the date refers
to the start date. If the end time is before the start time, we assume
it's the day after. Again, good enough for now.
|
|
|
|
|
|
|
| |
The way we had this until now with a date and separate start and end
times does not really work. There are cases when a screening starts on
one day, but ends on the next. By keeping a complete timestamp for both
the start and end times, we don't fall into this problem.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This makes each screening record self-contained, and the json
payload more consistent with how it semantically fit together.
|
| |
|
|
|
|
|
|
| |
Makes tha API a bit nicer by asking the database rather than
passing the database on to each model. Reserve models for
method/functions that work on the model structs themselves.
|
|
Not entirely happy about the way this turned out for now. A more ergonomic
return type from the models::screenings::get_all() function will be
investigated.
|