Age | Commit message (Collapse) | Author | Lines |
|
|
|
|
|
|
|
As a side effect, this turns the response of GET /journey/edit (which should
never happen in the first place) from an exception into a 404 error (#36)
|
|
|
|
Closes #27
|
|
|
|
Closes #19
|
|
|
|
|
|
only create DateTime objects when needed
|
|
|
|
|
|
Closes #25
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This issue was introduced in 7c7b5e9f9536f70c92d66c4055090b46e26c4c11 and
caused the client-side javascript code to crash
|
|
|
|
|
|
|
|
Not well-tested yet, deployment will have to wait a bit. Issue #15
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Closes #3
|
|
|
|
|
|
|
|
Todo: Redirect user to destination station upon arrival
|
|
Whether a user is in transit or not is now determined by an entry in the
in_transit table instead of a dangling checkin.
All completed journeys are stored in the "journeys" table.
This does most of the work needed for automatic checkout. However, note that
the corresponding worker process is not implemented yet.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
See issue #3
|