summaryrefslogtreecommitdiff
path: root/lib/Travelynx.pm
AgeCommit message (Collapse)AuthorLines
2024-10-28Use the correct stop instance when checking in to ring linesBirte Kristina Friesel-1/+9
2024-10-16Add terms of service andpoint; reference it from registration and login formsBirte Kristina Friesel-0/+1
2024-09-18API: Add departure and arrival platform2.8.39Birte Kristina Friesel-0/+2
Closes #164
2024-08-28Replace ice_names.json with Travel::Status::DE::DBWagenreihung built-in listBirte Kristina Friesel-2/+4
2024-08-26map, get_travel_distance: Prefer EVA ID over name for route matches2.8.33Birte Kristina Friesel-4/+10
Station names frequently change, so the EVA ID is more robust Closes #160
2024-08-25IRIS: Re-add support for stations unknown to T::S::DE::IRIS::Stations2.8.31Birte Kristina Friesel-0/+8
This fixes a regression introduced by 47f76da4f8cc31146d2834dfdf9731d330288c9d Closes #159 Journeys logged with travelynx v2.8.0 through 2.8.30 are affected by this bug and will contain incorrect data even after applying this patch – it only fixes data for new entries. To Do: See if affected entries can be repaired with a DB migration
2024-08-25fix /cancelled.jsonBirte Kristina Friesel-1/+2
Closes #155
2024-08-16improve hafas checkin error message for route issuesBirte Kristina Friesel-1/+2
2024-08-15stats, map: deal with multiple EVA IDs mapping to the same station nameBirte Kristina Friesel-0/+25
2024-08-14IRIS checkout: do not overwrite HAFAS route with IRIS routeBirte Kristina Friesel-1/+0
The IRIS route may differ from the HAFAS route in case of diversions, causing travelynx to lose real-time data, coordinates, and polyline when the follow-up add_route_timestamps call is not made.
2024-08-14add_route_timestamps: do not re-request trip id if it is already known2.8.17Birte Kristina Friesel-8/+19
2024-08-08Switch to new carriage formation APIBirte Kristina Friesel-42/+58
2024-07-26Multi-backend supportBirte Kristina Friesel-19/+47
Squashed commit of the following: commit 92518024ba295456358618c0e8180bd8e996fdf1 Author: Birte Kristina Friesel <birte.friesel@uos.de> Date: Fri Jul 26 18:39:46 2024 +0200 add_or_update station: remove superfluos 'new backend id := old backend id' commit df21c20c6e4c86454f8a9ac69121404415217f2a Author: Birte Kristina Friesel <birte.friesel@uos.de> Date: Fri Jul 26 18:35:51 2024 +0200 revert connection targets min_count to 3 commit be335cef07d0b42874f5fc1de4a1d13396e8e807 Author: Birte Kristina Friesel <birte.friesel@uos.de> Date: Fri Jul 26 18:20:05 2024 +0200 mention backend selection in API documentation commit 9f41828fb4f18fd707e0087def3032e8d4c8d7d8 Author: Birte Kristina Friesel <derf@finalrewind.org> Date: Thu Jul 25 20:19:23 2024 +0200 use_history: not all backends provide route data in departure monitor commit 09714b4d89684b8331d0e96f564a4c7432318f70 Author: Birte Kristina Friesel <derf@finalrewind.org> Date: Thu Jul 25 20:11:44 2024 +0200 disambiguation: pass correct hafas parameter commit 8cdf1120fc32155dc6525be64601b7c10a9c7f52 Author: Birte Kristina Friesel <derf@finalrewind.org> Date: Thu Jul 25 20:11:28 2024 +0200 _checked_in: hide Zuglauf link for non-db checkins commit 7455653f541198e0e0a6d11aed421487ffdb6285 Author: Birte Kristina Friesel <derf@finalrewind.org> Date: Thu Jul 25 20:01:47 2024 +0200 debug output commit b9cda07f85601a58ea32dbdacdd5399f302db52b Author: Birte Kristina Friesel <derf@finalrewind.org> Date: Thu Jul 25 19:09:07 2024 +0200 fix remaining get_connection_targets / get_connecting_trains_p invocations commit 2759d7258c37c7498905cfe19f6b4c4f6d16bd21 Author: Birte Kristina Friesel <derf@finalrewind.org> Date: Wed Jul 24 20:50:12 2024 +0200 support non-DB HAFAS backends (WiP)
2024-07-21Add lat/lon to pre-2.7.8 journeys; add eva where missingBirte Kristina Friesel-39/+38
This speeds up the map significantly and makes coordinates_by_station obsolete
2024-07-08store lat/lon along with route2.7.8Birte Kristina Friesel-0/+2
This increases resilience against EVA ID reuse
2024-06-23always use HAFAS for traewelling → travelynxBirte Kristina Friesel-199/+50
2024-06-21oopsie2.7.2Birte Kristina Friesel-1/+1
Closes #144
2024-06-21add_route_timestamps: use $train->id rather than in_transit id2.7.1Birte Kristina Friesel-1/+1
this avoids a race condition when the worker requests all current checkins and takes a while before getting to update the data
2024-06-15InTransit: allow setting data in add callBirte Kristina Friesel-5/+1
2024-06-15remove service / sb_template selection; hardcode DBF with variable hafas flagBirte Kristina Friesel-2/+1
2024-06-06allow force checkouts even in case of route mismatches2.6.16Birte Kristina Friesel-1/+1
2024-05-31Profile: Add JSON rendererBirte Kristina Friesel-1/+2
2024-05-30DBDB: use realtime cache for carriage composition requestsBirte Kristina Friesel-5/+6
2024-05-30perform stationinfo requests for hafas checkinsBirte Kristina Friesel-3/+19
2024-05-29request wagon orders for HAFAS checkinsBirte Kristina Friesel-1/+5
2024-05-29Move wagonorder request to a separate helperBirte Kristina Friesel-93/+109
This is in preparation for HAFAS wagonorder support
2024-05-24check train/trip id when updating associated dataBirte Kristina Friesel-17/+26
this avoid race conditions when a user changes their checkin between the time of request (old trip id) and the time of data update (new trip id). These could lead to funny effects such as buses suddenly having S-Bahn carriage formations.
2024-05-22add_route_timestamps: IRIS route may be shorter than HAFAS route2.6.11Birte Kristina Friesel-1/+1
2024-05-22Use HAFAS routes as single source of truth. Overwrite initial IRIS route.Birte Kristina Friesel-35/+47
2024-04-26/status: respond to .json as well as "Accept: application/json"Birte Kristina Friesel-2/+4
2024-04-21refactor polyline insertion into InTransit ModelBirte Kristina Friesel-95/+9
2024-04-07Request polylines for HAFAS journeys as well; only store sensible ones2.6.5Birte Kristina Friesel-1/+91
Decreases severity of #99 Fixes #108
2024-02-24Use journeyMatch rather than legacy trainsearch.exe API to find tripIDsBirte Kristina Friesel-55/+4
2023-12-27Switch to Travel::Status::DE::HAFAS 5.xBirte Kristina Friesel-1/+2
2023-09-16journey: show distances below 10km with 100m resolution (and <1km with 1m)Birte Kristina Friesel-0/+14
2023-09-12map: use high beeline opacity if no polylines are available2.2.1Birte Kristina Friesel-1/+5
2023-09-07Fix intermediate stop display for journeys without real-time data, e.g. H-BahnBirte Kristina Friesel-15/+11
2023-08-30API: Expose HAFAS JourneyID, if available (#85)Birte Kristina Friesel-4/+5
2023-08-26obtain autocompletion from database2.1.1Birte Kristina Friesel-0/+1
2023-08-19API: Support HAFAS checkin (via journeyID)Birte Kristina Friesel-1/+2
2023-08-13synchronize non-train checkins from traewelling to travelynxBirte Kristina Friesel-14/+79
2023-08-13WIP: HAFAS supportBirte Kristina Friesel-9/+191
2023-08-07Traewelling: replace legacy password login with OAuth2Birte Kristina Friesel-0/+22
This is a breaking change insofar as that traewelling support is no longer provided automatically, but must be enabled by providing a traewelling.de application ID and secret in travelynx.conf. However, as traewelling.de password login is deprecated and wil soon be disabled, travelynx would break either way. So we might or might not see travelynx 2.0.0 in the next days. Automatic token refresh is still todo, but that was the case for password login as well. Closes #64
2023-07-23convert checkout to promises (checkout_p)Birte Kristina Friesel-186/+221
2023-07-23checkout: remove with_related special caseBirte Kristina Friesel-35/+12
travelynx now always calls checkout with the database-provided arr_eva, so the edge case in which it provided a station that is not actually on the route of a train can no longer appear.
2023-07-15remove debug outputBirte Kristina Friesel-3/+0
2023-07-15add timeline / current checkinsBirte Kristina Friesel-0/+1
2023-07-15get_user_status: fix stop_before_dest calculationBirte Kristina Friesel-4/+12
2023-07-15postprocess timeline; move user-related parts to get_user_statusBirte Kristina Friesel-0/+36
2023-07-15increase maximum comment lengthBirte Kristina Friesel-49/+49