summaryrefslogtreecommitdiff
path: root/lib/Travelynx/Controller
AgeCommit message (Collapse)AuthorLines
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-09-18handle substitute connections in passenger rights formDaniel Friesel-2/+35
2019-09-18passengerrights: improve support for cancelled trainsDaniel Friesel-9/+52
To do: also do so in form generation
2019-09-14improve connection detection heuristicDaniel Friesel-1/+21
2019-09-13add passenger rights heuristic for missed connectionsDaniel Friesel-12/+172
2019-09-12add auto-generated passenger rights forms1.9.0Daniel Friesel-0/+83
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-20show journey suggestions on departure board as well1.6.0Daniel Friesel-0/+32
2019-05-19allow checkin from connections viewDaniel Friesel-1/+15
2019-05-14Show web-hook test result immediately after saving it1.3.3Daniel Friesel-3/+12
Closes #12
2019-05-11history: validate year and monthDaniel Friesel-2/+12
2019-05-10Add webhook to account pageDaniel Friesel-1/+4
2019-05-06basic webhook support, onwards to betatestingDaniel Friesel-64/+2
2019-05-05WiP webhook supportDaniel Friesel-0/+25
2019-05-03data export: use station names, not IDs1.1.4Daniel Friesel-2/+2
2019-05-03Experimental PWA support (#13)Daniel Friesel-0/+6
2019-05-03Add changelogDaniel Friesel-0/+7
2019-05-02Do not error out when receiving UIDs > INT_MAX1.1.2Daniel Friesel-1/+16
2019-05-02Public API documentationDaniel Friesel-0/+6
2019-05-02Finish public-facing exposed user status (opt-in)Daniel Friesel-2/+4
2019-04-30Prepare settings and templates for opt-in public travel statusDaniel Friesel-0/+60
2019-04-30show imprint and version on landing pageDaniel Friesel-1/+7
2019-04-30use a separate table for registration tokensDaniel Friesel-7/+3
2019-04-30Implement deletion of inactive accountsDaniel Friesel-0/+4
2019-04-30allow users to change their mail address0.19Daniel Friesel-1/+99
Closes #6
2019-04-30Move invalid input errors into common sub-templateDaniel Friesel-4/+5
2019-04-29Add password reset functionalityDaniel Friesel-0/+154
Closes #5
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-24Bump API to v1Daniel Friesel-1/+108
2019-04-24export: Add in_transit fieldDaniel Friesel-1/+5
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-96/+71
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-30/+38
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-10 02:12:06 +0000