summaryrefslogtreecommitdiff
path: root/src (follow)
Commit message (Collapse)AuthorAgeFilesLines
* print less formatting errors in timesHEADmainstuebinm2024-09-091-8/+18
| | | | | | | | | | | | | | these used to go wrong in case there was no real-time info on departure times. Instead traveltext now falls back on scheduled departure times if no real-time info is available. These still fail sometimes (at exit-only stops both appear to be unset on the oebb hafas), but it's a lot better than what was before. Also I've observed travelynx returning actual null values for missing time stamps now, so the old hack of checking if timestamp = unix epoch and considering that "unknown" might no longer be necessary, but I'm keeping it around just in case.
* update dependencies, hafas-rs -> railway-provider-hafasstuebinm2024-09-091-27/+27
| | | | | | | turns out the old hafas-rs project that started with trainsear.ch has since been picked up by some gnome people who use it for their (creatively named) Railway app. It's a lot more general now, though the documentation doesn't seem to have improved much 🙃
* do not require ds100 codes in API responsesstuebinm2024-09-095-12/+12
| | | | | these are not present when other hafas backends than the DB one were used for the trip's checkin.
* switch to another fork of hafas-rsstuebinm2023-04-171-0/+3
| | | | (yuka's version is no longer maintained & broke)
* handle unknown times at stationsstuebinm2022-11-281-3/+11
| | | | | | (travelynx sends these as the literal epoch value, which led to really confusing results, printing exactly the time zone offset as arrival time)
* add import from hafas to travelynxstuebinm2022-04-211-10/+134
| | | | (using yuka's hafas-rs)
* from / to commands for travelynxstuebinm2022-02-263-10/+50
|
* fix the Trip type (and make it Display)stuebinm2022-02-264-34/+36
| | | | it's not as nice as i'd like, but whatever
* iceportal: cancelled stops have state nullstuebinm2022-02-261-1/+2
| | | | which … fine, i guess
* existential types in rust are weirdstuebinm2022-02-098-202/+312
| | | | … lots and lots of traits …
* S-Bahns are weirdstuebinm2022-02-083-1/+123
| | | | (added a simple zugportal.de api client, but can't do auto-checkin yet)
* we'll be there in -1000 minutes isn't helpfulstuebinm2022-02-023-4/+14
|
* pretty print pretty printing codestuebinm2022-02-016-457/+485
|
* are we there yet?stuebinm2022-02-012-1/+24
| | | | | (also why do people get up from their seats a solid nine minutes before the train is even scheduled to arrive at all?)
* handle (esp. iceportal) timestamps correctlystuebinm2022-02-014-61/+68
| | | | | why use unix time if you can use unix time * 1000 while your margin of error will never be lower than a full minute?
* display iceportal itinery & stopsstuebinm2022-02-016-28/+80
| | | | | | | I'm pretty sure something in parsing the times is broken, since this train is currently /also/ broken I have absolutely no idea what the correct ones would be and don't have the energy to dig further into this.
* better output if there are no intermediate stopsstuebinm2022-02-011-10/+8
|
* add `traveltext destination`stuebinm2022-02-012-0/+19
| | | | I have no intention of going to Hamburg today, so I need to check out earlier
* sadly i'm not on a ICE right nowstuebinm2022-01-261-4/+10
|
* add a config file because why notstuebinm2022-01-261-24/+65
|
* some code deduplicationsstuebinm2022-01-251-69/+88
|
* hacky proof of conceptstuebinm2022-01-255-0/+489
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-22 04:05:29 +0000