summaryrefslogtreecommitdiff
path: root/lib/Travelynx.pm
AgeCommit message (Collapse)AuthorLines
2019-11-20allow routes to be edited after recording a journeyDaniel Friesel-0/+30
2019-11-19allow route input when adding journeys manually (#26)Daniel Friesel-12/+34
2019-11-16move station -> location map to generic helperDaniel Friesel-0/+15
2019-11-16add map view of past journeys. unfinished and unreferenced.Daniel Friesel-0/+1
2019-11-12Fix implicit checkout when checking in from a related station1.9.10Daniel Friesel-0/+15
Previously, realtime data was missing in this case
2019-10-29live update of next station via javascriptDaniel Friesel-0/+30
2019-10-25route diff: remove debug outputDaniel Friesel-3/+0
2019-10-19show related stations in departure list1.9.7Daniel Friesel-0/+1
2019-10-06Travelynx.pm: Document the real cause of sched_arr-isa-DateTime bugDaniel Friesel-13/+6
2019-10-06derp1.9.5Daniel Friesel-2/+2
2019-10-06Work around crash when a train has the same stop more than once1.9.4Daniel Friesel-2/+18
2019-10-04mark cancelled stops in checkin viewDaniel Friesel-2/+51
2019-09-18Save scheduled arrival time for cancelled trains1.9.3Daniel Friesel-4/+7
2019-09-13add passenger rights heuristic for missed connectionsDaniel Friesel-0/+1
2019-09-12Explicitly set passenger rights form filename1.9.1Daniel Friesel-1/+1
2019-09-12add auto-generated passenger rights forms1.9.0Daniel Friesel-0/+2
2019-08-23Allow comments to be editedDaniel Friesel-3/+14
2019-08-23Add proper journey comment supportDaniel Friesel-2/+5
2019-08-13Fix beeline distance calculation when start/stop has no geo-coordinates1.8.7Daniel Friesel-17/+37
2019-08-06show boarding countdown in departure overviewDaniel Friesel-8/+31
2019-08-03also show train direction on departureDaniel Friesel-3/+53
2019-08-03move exit direction calculation to a helper functionDaniel Friesel-47/+52
2019-07-20Handle race condition when several workers are updating the same history entry1.8.5Daniel Friesel-7/+25
2019-07-14Show departures of all linked stationsDaniel Friesel-6/+8
Not well-tested yet, deployment will have to wait a bit. Issue #15
2019-07-14handle ambiguous train numbers when requesting train details1.8.3Daniel Friesel-2/+10
2019-06-25Fix wrong directions on long-distance arrivalsDaniel Friesel-2/+4
2019-06-24show wagon order before departure1.8.0Daniel Friesel-0/+20
2019-06-23also show exit direction for regional trains at select stationsDaniel Friesel-0/+14
2019-06-23also show exit direction based on wagon orderDaniel Friesel-0/+33
2019-06-22show exit direction on kopfgleis platformsDaniel Friesel-44/+114
2019-06-19disable wagonorder for now (not used yet anyway)1.7.5Daniel Friesel-28/+29
2019-06-17prepare for wagon order supportDaniel Friesel-11/+75
2019-06-07connections: order by realtime, not scheduled departure1.7.3Daniel Friesel-1/+5
2019-06-04checked in: Show QoS messages before departure and HIM messages at all timesDaniel Friesel-3/+42
2019-06-01Work around Safari violating the spec for SameSite=Lax cookies1.7.2Daniel Friesel-0/+15
This fixes users being logged out whenever following an external link to travelynx in Safari (iOS/macOS)
2019-06-01run update hook after setting arrival timeDaniel Friesel-1/+1
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
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-13 18:22:22 +0000