Age | Commit message (Collapse) | Author | Lines |
|
When a user changes their destination station or checks into a new train
while work is updating data for their in_transit entry, values for no longer
valid database entrie would be entered.
|
|
|
|
|
|
|
|
Requires Travel::Status::DE::IRIS v1.38 (not released yet)
|
|
|
|
This was broken by a database migration introduced in
commit f6d56d3134f6045726cb1d4ed8700382575bb686
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Closes #6
|
|
|
|
Closes #5
|
|
|
|
Closes #11
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
Reported by @marudor
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Provides a workaround for #2
|
|
|
|
|
|
|
|
|