summaryrefslogtreecommitdiff
path: root/lib/Travelynx.pm
AgeCommit message (Collapse)AuthorLines
2019-06-01Set arrival time via HAFAS if not available from IRISDaniel Friesel-1/+27
2019-05-31show current/next stop while checked inDaniel Friesel-4/+262
2019-05-29use journey-specific status links -> one twitter card per journeyDaniel Friesel-0/+2
2019-05-26Use JSON for messages and route storage, prepare for extended route dataDaniel Friesel-35/+46
2019-05-24Fix missing update event when arrival time at destination is unknown1.6.1Daniel Friesel-0/+1
2019-05-24Increase suggestion time range to 4 monthsDaniel Friesel-1/+1
2019-05-20show journey suggestions on departure board as well1.6.0Daniel Friesel-18/+94
2019-05-20Handle accidental double-checkins1.5.1Daniel Friesel-2/+8
2019-05-19allow checkin from connections viewDaniel Friesel-5/+14
2019-05-19Work in progress: show connections when arriving soonDaniel Friesel-0/+111
At the moment, the heuristic used to determine connection targets is quite simple: $station is a target iff there were at least two trips in the past 6 weeks with checkin at the current destination station and checkout at $station. Todo / enhanhement options: * Consider current origin station as well, i.e.: $station is a target iff there were at least two trips in the past 6 weeks which are preceded by a trip from the current origin station and (same as above) * Make connection links clickable once the current journey has ended. Connections need to be added to _checked_out as well for this to work.
2019-05-18Show arrival/departure platform in journey cardDaniel Friesel-0/+7
2019-05-18Pre-select theme css in backendDaniel Friesel-0/+17
2019-05-14Show web-hook test result immediately after saving it1.3.3Daniel Friesel-2/+16
Closes #12
2019-05-11get_journey_stats: Support uid override, fix uninitialized value warningDaniel Friesel-3/+6
2019-05-10Add webhook to account pageDaniel Friesel-1/+1
2019-05-09set a custom user agentDaniel Friesel-1/+5
2019-05-08Fix division by zero when calculating journey completion1.1.9Daniel Friesel-2/+5
2019-05-06basic webhook support, onwards to betatestingDaniel Friesel-5/+79
2019-05-05WiP webhook supportDaniel Friesel-0/+113
2019-05-03Experimental PWA support (#13)Daniel Friesel-0/+1
2019-05-03use /account/... links for mail/password changeDaniel Friesel-4/+4
2019-05-03Do not show origin station in destination list1.1.3Daniel Friesel-3/+3
2019-05-03Add changelogDaniel Friesel-0/+1
2019-05-02Public API documentationDaniel Friesel-0/+1
2019-05-02Finish public-facing exposed user status (opt-in)Daniel Friesel-0/+1
2019-04-30Prepare settings and templates for opt-in public travel statusDaniel Friesel-0/+35
2019-04-30use a separate table for registration tokensDaniel Friesel-10/+27
2019-04-30Implement deletion of inactive accountsDaniel Friesel-3/+15
2019-04-30allow users to change their mail address0.19Daniel Friesel-1/+55
Closes #6
2019-04-29Add password reset functionalityDaniel Friesel-0/+85
Closes #5
2019-04-28Handle inconsistent data when calculating monthly/yearly statsDaniel Friesel-7/+18
Closes #11
2019-04-27History: Only show months and years with logged journeysDaniel Friesel-0/+41
2019-04-26Invalidate stats cache after adding a new journeyDaniel Friesel-0/+1
2019-04-26add_journey: Fix incorrect return in case of unmatched stationDaniel Friesel-2/+2
2019-04-26Add manual journey entryDaniel Friesel-68/+64
Closes #3
2019-04-24show recent delay/qos messages in checked_in view0.16Daniel Friesel-0/+10
2019-04-24Bump API to v1Daniel Friesel-0/+1
2019-04-23Remove legacy action_type attributesDaniel Friesel-17/+2
2019-04-23Primitive auto-refresh of current journey statusDaniel Friesel-0/+1
Todo: Redirect user to destination station upon arrival
2019-04-23Automatic checkout \o/Daniel Friesel-10/+34
2019-04-23Use one row per journey instead of split checkin/checkout entriesDaniel Friesel-423/+378
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-22Finish transition from DBI to Mojo::PgDaniel Friesel-18/+0
2019-04-22Use Mojo::Pg for all remaining Controller and Helper logicDaniel Friesel-64/+27
2019-04-22Also use Mojo::Pg for user_status and user_travels queriesDaniel Friesel-154/+127
2019-04-22More Mojo::Pg migrationsDaniel Friesel-223/+141
2019-04-21Ignore stations without coordinates in distance calculationDaniel Friesel-6/+32
Reported by @marudor
2019-04-19refactor set_status_query and get_token_queryDaniel Friesel-29/+8
2019-04-17Refactor user_actions insert/update/delete statements with Mojo::PgDaniel Friesel-248/+230
2019-04-17Initiate transition to Mojo::PgDaniel Friesel-57/+77
2019-04-14Set version via configDaniel Friesel-2/+0