traveltext - travelynx terminal client

	Commit message (Collapse)	Author	Files	Lines
2024-09-09	print less formatting errors in timesHEAD main	stuebinm	1	-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.
2024-09-09	update dependencies, hafas-rs -> railway-provider-hafas	stuebinm	1	-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 🙃
2024-09-09	do not require ds100 codes in API responses	stuebinm	5	-12/+12
	these are not present when other hafas backends than the DB one were used for the trip's checkin.
2023-04-17	switch to another fork of hafas-rs	stuebinm	1	-0/+3
	(yuka's version is no longer maintained & broke)
2022-11-28	handle unknown times at stations	stuebinm	1	-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)
2022-04-21	add import from hafas to travelynx	stuebinm	1	-10/+134
	(using yuka's hafas-rs)
2022-02-26	from / to commands for travelynx	stuebinm	3	-10/+50

2022-02-26	fix the Trip type (and make it Display)	stuebinm	4	-34/+36
	it's not as nice as i'd like, but whatever
2022-02-26	iceportal: cancelled stops have state null	stuebinm	1	-1/+2
	which … fine, i guess
2022-02-09	existential types in rust are weird	stuebinm	8	-202/+312
	… lots and lots of traits …
2022-02-08	S-Bahns are weird	stuebinm	3	-1/+123
	(added a simple zugportal.de api client, but can't do auto-checkin yet)
2022-02-02	we'll be there in -1000 minutes isn't helpful	stuebinm	3	-4/+14

2022-02-01	pretty print pretty printing code	stuebinm	6	-457/+485

2022-02-01	are we there yet?	stuebinm	2	-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?)
2022-02-01	handle (esp. iceportal) timestamps correctly	stuebinm	4	-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?
2022-02-01	display iceportal itinery & stops	stuebinm	6	-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.
2022-02-01	better output if there are no intermediate stops	stuebinm	1	-10/+8

2022-02-01	add `traveltext destination`	stuebinm	2	-0/+19
	I have no intention of going to Hamburg today, so I need to check out earlier
2022-01-26	sadly i'm not on a ICE right now	stuebinm	1	-4/+10

2022-01-26	add a config file because why not	stuebinm	1	-24/+65

2022-01-25	some code deduplications	stuebinm	1	-69/+88