summaryrefslogtreecommitdiff
path: root/lib/Travelynx/Model
AgeCommit message (Collapse)AuthorLines
2024-07-21Stations: Remove get_latlon_by_name (no longer needed)2.7.9Birte Kristina Friesel-14/+0
2024-07-21Add lat/lon to pre-2.7.8 journeys; add eva where missingBirte Kristina Friesel-9/+8
This speeds up the map significantly and makes coordinates_by_station obsolete
2024-07-21Journey->add: store lat/lon for route at entry time, if availableBirte Kristina Friesel-4/+33
2024-07-08store lat/lon along with route2.7.8Birte Kristina Friesel-2/+6
This increases resilience against EVA ID reuse
2024-06-15InTransit: allow setting data in add callBirte Kristina Friesel-2/+9
2024-06-15remove service / sb_template selection; hardcode DBF with variable hafas flagBirte Kristina Friesel-36/+3
2024-06-15recent journeys: use hafas=DB as wellBirte Kristina Friesel-1/+1
2024-06-15Use hafas=DB rather than hafas=12.6.22Birte Kristina Friesel-1/+4
2024-06-08Store journey backend; do not rely on '|' in ID to distinguish IRIS/HAFASBirte Kristina Friesel-1/+17
This is in preparation for supporting multiple HAFAS backends, and possibly EFA and RIS::Journeys.
2024-06-06... derp2.6.18Birte Kristina Friesel-4/+1
2024-06-06traewelling pull sync requires user_name to be set2.6.17Birte Kristina Friesel-1/+4
2024-05-24check train/trip id when updating associated dataBirte Kristina Friesel-17/+31
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-22route_after: handle passing the same stop more than once2.6.10Birte Kristina Friesel-2/+9
2024-05-09InTransit: postprocess: simplify DateTime handling a bitBirte Kristina Friesel-21/+25
2024-04-21refactor polyline insertion into InTransit ModelBirte Kristina Friesel-0/+55
2024-04-16Store HAFAS checkins with type/train/line number at checkin station2.6.7Birte Kristina Friesel-3/+5
2024-04-03store tz_offset in route data if presentBirte Kristina Friesel-1/+7
2024-02-13Journeys: adjust sanity_check for local transit stuff2.5.17Birte Kristina Friesel-7/+7
2024-02-09add dumpstops command2.5.16Birte Kristina Friesel-0/+6
2023-12-27Switch to Travel::Status::DE::HAFAS 5.xBirte Kristina Friesel-28/+29
2023-10-01suggested connections: avoid fetching IRIS trains via HAFASBirte Kristina Friesel-3/+6
2023-10-01store related stations; respect them when looking up connectionsBirte Kristina Friesel-14/+48
2023-09-24intransit: support HAFAS trains that do not have a typeBirte Kristina Friesel-1/+1
2023-09-24add support for HAFAS connection suggestions; drop manual destination listBirte Kristina Friesel-27/+3
Still TODO: handle stations that have several EVAs
2023-09-09indicate whether current journey has realtime dataBirte Kristina Friesel-3/+9
2023-09-07Fix intermediate stop display for journeys without real-time data, e.g. H-BahnBirte Kristina Friesel-4/+8
2023-08-26obtain autocompletion from database2.1.1Birte Kristina Friesel-0/+13
2023-08-22select latest journey based on timestamp, not ID2.0.2Birte Kristina Friesel-1/+1
This avoids manually added past journeys messing with the latest travel target
2023-08-16recent targets: distinguish hafas/irisBirte Kristina Friesel-3/+4
2023-08-13WIP: HAFAS supportBirte Kristina Friesel-21/+198
2023-08-09Store traewelling refresh token in database1.34.3Birte Kristina Friesel-12/+13
2023-08-07Traewelling: replace legacy password login with OAuth2Birte Kristina Friesel-4/+3
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-19Users->delete: delete relations as well1.33.6Birte Kristina Friesel-9/+11
2023-07-18followee list: show if accounts are following back1.33.3Birte Kristina Friesel-2/+20
2023-07-16account: add a list of sent follow requestsBirte Kristina Friesel-9/+11
2023-07-16show followee checkins in departure boardBirte Kristina Friesel-1/+1
2023-07-15postprocess timeline; move user-related parts to get_user_statusBirte Kristina Friesel-152/+131
2023-07-15timeline: minimum visibility is followers-only, not unlistedBirte Kristina Friesel-1/+1
2023-07-15Move InTransit post-processing to InTransit moduleBirte Kristina Friesel-0/+168
2023-07-15add view for followees in transitBirte Kristina Friesel-0/+32
2023-07-14Journeys->get_latest: Fix uninitialized value warningBirte Kristina Friesel-12/+16
2023-07-13get_pushable_accounts: obtain all values from in_transit_strBirte Kristina Friesel-8/+7
2023-07-13Checkin: Use correct visibility when pushing to TräwellingnetworkException-1/+3
2023-07-03journeys: simplify visibily checkDerf Null-12/+1
2023-07-03update ALL the copyright notices!Derf Null-6/+6
2023-07-02show hours and minutes until arrival, not just minutesDerf Null-15/+17
2023-06-28Journey->add_from_in_transit: return ID of added journeyDerf Null-1/+2
2023-06-27journeys: return effective visibilityDerf Null-24/+31
2023-06-26compute effective visibility in database viewDerf Null-7/+9
2023-06-26Move hash_password to Model/UsersDerf Null-3/+12