summaryrefslogtreecommitdiff
path: root/lib/Travelynx/Controller/Traveling.pm
AgeCommit message (Collapse)AuthorLines
2020-01-25map: list skipped journeys1.13.7Daniel Friesel-0/+8
2020-01-25map: support multiple polyline groups with different colorsDaniel Friesel-2/+9
2020-01-19Return HTTP 404 for unknown journeysDaniel Friesel-0/+4
2020-01-19/journey/:id: verify that id is numericDaniel Friesel-1/+1
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)
2019-12-26fix connections display1.12.2Daniel Friesel-1/+1
2019-12-08allow a journey's cancellation status to be edited1.11.1Daniel Friesel-0/+12
Closes #27
2019-12-08Allow status visibility to be limited to travelynx usersDaniel Friesel-2/+17
2019-12-06optionally show journey comment in public user statusDaniel Friesel-5/+7
Closes #19
2019-12-06Allow comments to be entered while still in transitDaniel Friesel-0/+45
2019-11-27history map: Add checkbox to display manually added journeysDaniel Friesel-2/+20
2019-11-24improve get_user_travels performance, most notably when rendering map1.10.3Daniel Friesel-21/+24
only create DateTime objects when needed
2019-11-20allow routes to be edited after recording a journeyDaniel Friesel-0/+14
2019-11-19allow route input when adding journeys manually (#26)Daniel Friesel-1/+5
2019-11-18add journey: make realtime data optional (default to schedule data)1.10.1Daniel Friesel-0/+3
Closes #25
2019-11-16history map: show time range; handle users with no journeysDaniel Friesel-2/+22
2019-11-16history map: Do not show route for manually added journeysDaniel Friesel-1/+1
2019-11-16history map: skip duplicates earlierDaniel Friesel-11/+25
2019-11-16map_history: uniq_by_route did not consider the actual passenger route, scrap itDaniel Friesel-5/+1
2019-11-16map: add legend, link to history map from history pageDaniel Friesel-1/+1
2019-11-16move station -> location map to generic helperDaniel Friesel-11/+6
2019-11-16map: add station names to pointsDaniel Friesel-1/+1
2019-11-16add map view of past journeys. unfinished and unreferenced.Daniel Friesel-0/+62
2019-10-19Fix invalid geolocation list when less than 5 unique station names are nearby1.9.8Daniel Friesel-5/+14
This issue was introduced in 7c7b5e9f9536f70c92d66c4055090b46e26c4c11 and caused the client-side javascript code to crash
2019-10-19show related stations in departure list1.9.7Daniel Friesel-4/+5
2019-08-23Allow comments to be editedDaniel Friesel-0/+19
2019-07-20Do not show station duplicates in geolocation list1.8.4Daniel Friesel-2/+4
2019-07-14Show departures of all linked stationsDaniel Friesel-1/+1
Not well-tested yet, deployment will have to wait a bit. Issue #15
2019-05-29use journey-specific status links -> one twitter card per journeyDaniel Friesel-2/+11
2019-05-29add twitter preview tags to public user status pageDaniel Friesel-1/+30
2019-05-26Use JSON for messages and route storage, prepare for extended route dataDaniel Friesel-4/+0
2019-05-19allow checkin from connections viewDaniel Friesel-1/+15
2019-05-11history: validate year and monthDaniel Friesel-2/+12
2019-05-02Finish public-facing exposed user status (opt-in)Daniel Friesel-0/+2
2019-04-30Prepare settings and templates for opt-in public travel statusDaniel Friesel-0/+38
2019-04-30show imprint and version on landing pageDaniel Friesel-1/+7
2019-04-30Implement deletion of inactive accountsDaniel Friesel-0/+2
2019-04-26Add manual journey entryDaniel Friesel-21/+44
Closes #3
2019-04-25undo: Redirect to departure station when undoing a checkinDaniel Friesel-1/+6
2019-04-24$render(status => ...) is a special variable. derp.Daniel Friesel-2/+2
2019-04-23Fix checkin/checkout of cancelled journeysDaniel Friesel-4/+2
2019-04-23Primitive auto-refresh of current journey statusDaniel Friesel-0/+14
Todo: Redirect user to destination station upon arrival
2019-04-23Use one row per journey instead of split checkin/checkout entriesDaniel Friesel-51/+50
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.
2019-04-22Use Mojo::Pg for all remaining Controller and Helper logicDaniel Friesel-20/+13
2019-04-17Refactor user_actions insert/update/delete statements with Mojo::PgDaniel Friesel-1/+1
2019-04-13work-in-progress manual journey entry. incomplete and not enabled yet.Daniel Friesel-4/+70
2019-04-08Work-in-progress journey editor. Not ready for deployment.Daniel Friesel-8/+59
2019-04-07Prepare forms for manual journey entry and editingDaniel Friesel-0/+58
2019-04-07Refactor history template, add yearly statsDaniel Friesel-14/+57
2019-04-07Cache journey statsDaniel Friesel-6/+9
2019-04-04Allow journey deletionDaniel Friesel-5/+28
See issue #3