| Commit message (Collapse) | Author | Files | Lines | ||
|---|---|---|---|---|---|
| 2024-09-09 | do not require ds100 codes in API responsesHEADmain | stuebinm | 1 | -2/+2 | |
| these are not present when other hafas backends than the DB one were used for the trip's checkin. | |||||
| 2022-02-26 | fix the Trip type (and make it Display) | stuebinm | 1 | -6/+6 | |
| 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 | 1 | -7/+34 | |
| … lots and lots of traits … | |||||
| 2022-02-02 | we'll be there in -1000 minutes isn't helpful | stuebinm | 1 | -1/+1 | |
| 2022-02-01 | pretty print pretty printing code | stuebinm | 1 | -55/+54 | |
| 2022-02-01 | handle (esp. iceportal) timestamps correctly | stuebinm | 1 | -8/+8 | |
| 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 | 1 | -3/+36 | |
| 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. | |||||
 |
index : traveltext | |
| travelynx terminal client |
| summaryrefslogtreecommitdiff |