From e168d9cd39c38b8e5a1994c8bf11376d26e9ea77 Mon Sep 17 00:00:00 2001
From: Daniel Friesel <derf@finalrewind.org>
Date: Tue, 23 Apr 2019 18:08:07 +0200
Subject: Use one row per journey instead of split checkin/checkout entries

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.
---
 templates/edit_journey.html.ep | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'templates/edit_journey.html.ep')

diff --git a/templates/edit_journey.html.ep b/templates/edit_journey.html.ep
index 0418d52..c37adba 100644
--- a/templates/edit_journey.html.ep
+++ b/templates/edit_journey.html.ep
@@ -80,7 +80,7 @@
 		</div>
 		<div class="row">
 			<div class="col s6 m6 l6 center-align">
-				<a href="/journey/<%= current_user()->{id} %>-<%= param('journey_id') %>" class="waves-effect waves-light btn">
+				<a href="/journey/<%= param('journey_id') %>" class="waves-effect waves-light btn">
 					Abbrechen
 				</a>
 			</div>
-- 
cgit v1.2.3