- Sep 06, 2020
-
-
Birte Kristina Friesel authored
-
- Sep 05, 2020
-
-
Birte Kristina Friesel authored
Closes #44
-
Birte Kristina Friesel authored
-
- Sep 04, 2020
-
-
Birte Kristina Friesel authored
- Sep 03, 2020
-
-
Birte Kristina Friesel authored
-
- Aug 28, 2020
-
-
Birte Kristina Friesel authored
-
- Aug 23, 2020
-
-
Birte Kristina Friesel authored
-
- Aug 22, 2020
-
-
Birte Kristina Friesel authored
-
- Aug 19, 2020
-
-
Birte Kristina Friesel authored
-
- Aug 16, 2020
-
-
Birte Kristina Friesel authored
-
- Aug 15, 2020
-
-
Birte Kristina Friesel authored
-
- Aug 06, 2020
-
-
Birte Kristina Friesel authored
-
- Jul 28, 2020
-
-
Birte Kristina Friesel authored
-
Birte Kristina Friesel authored
-
- Jul 27, 2020
-
-
Birte Kristina Friesel authored
-
- Jul 11, 2020
-
- Jun 13, 2020
-
-
Birte Kristina Friesel authored
-
Birte Kristina Friesel authored
Work in progress. Only status is documented at the moment.
-
- Apr 19, 2020
-
-
Birte Kristina Friesel authored
-
Birte Kristina Friesel authored
-
Birte Kristina Friesel authored
-
Birte Kristina Friesel authored
-
Birte Kristina Friesel authored
Select top station on work days (Mo .. Fr) with arrival < 13:00 or departure >= 13:00.
-
Birte Kristina Friesel authored
-
Birte Kristina Friesel authored
-
Birte Kristina Friesel authored
-
Birte Kristina Friesel authored
order is ascending by default, resulting in flop instead of top destinations.
-
Birte Kristina Friesel authored
-
Birte Kristina Friesel authored
- Apr 16, 2020
-
-
Birte Kristina Friesel authored
-
Birte Kristina Friesel authored
Until now, tripIDs were cached based on station and departure timestamp. These are identical for any two trains departing at the same time at the same station, leading to one of those getting being assigned a wrong tripID. From now on, only the JSON reported by transport.rest is cached -- tripIDs are always recomputed based on it.
-
Birte Kristina Friesel authored
- Apr 14, 2020
-
-
Birte Kristina Friesel authored
Closes #40
-
Birte Kristina Friesel authored
Previously, for each destination, up to two departures between now and now + 40 minutes were shown. When performing a fresh checkin (i.e., the has not logged a journey in the past few minutes and is not currently checked in), the departure list now additionally contains all departures between now - 5 minutes and now. When checking in from a train (i.e., the user has recently checked out at the station or is still checked in), it additionally contains all departures between arrival time and now. Closes #33
-
- Apr 06, 2020
-
-
Birte Kristina Friesel authored
Squashed commit of the following: commit 3dd25e35bb8c9d238e64300494b8c4e05e494bba Author: Daniel Friesel <derf@finalrewind.org> Date: Mon Apr 6 10:02:57 2020 +0200 hm commit 04159061ed7932e2ee4ceca7af9d43a3fca034c5 Author: Daniel Friesel <derf@finalrewind.org> Date: Mon Apr 6 09:56:19 2020 +0200 no sudo commit 1d16ec10faa807672433cbab11acd50eee9c8a6f Author: Daniel Friesel <derf@finalrewind.org> Date: Mon Apr 6 09:51:54 2020 +0200 Switch from Travis CI to GitHub Actions
-
- Mar 14, 2020
-