Commits · 4489fff0022430131ebfc6dc0499e9cdf0464aff · PIM / Itinerary

05 Jan, 2019 1 commit
- Merge journey results from multiple sources · 4489fff0
  Volker Krause authored Jan 05, 2019
  
  4489fff0
03 Jan, 2019 1 commit
- Support real-time journey data · e96b5266
  Volker Krause authored Jan 03, 2019
  
  e96b5266
15 Dec, 2018 4 commits
- Port journey queries to the backend abstraction too · 37f40d86
  Volker Krause authored Dec 15, 2018
  
  37f40d86
- Port departure query to use the new backend abstraction · e0ee7928
  Volker Krause authored Dec 15, 2018
```
We are now receiving departure data from Navitia and SNCF for suitable
locations. This still needs proper result merging though, as this can
result in duplicates.
```
  e0ee7928
- Make requests accessible from reply classes · 03e5179e
  Volker Krause authored Dec 15, 2018
  
  03e5179e
- Refactor reply classes to have a common base class · ad8302bb
  Volker Krause authored Dec 15, 2018
  
  ad8302bb
12 Dec, 2018 1 commit
- Post-process journey data to fill timezone information gaps · 141dca3c
  Volker Krause authored Dec 12, 2018
  
  141dca3c
08 Dec, 2018 1 commit
- Propagate backend errors · 056c192d
  Volker Krause authored Dec 08, 2018
  
  056c192d
07 Dec, 2018 1 commit
- Expand journey request to cover arrival/departure time search options · ac6a7153
  Volker Krause authored Dec 07, 2018
  
  ac6a7153
05 Dec, 2018 1 commit

Volker Krause authored Dec 05, 2018

Still misses error handling etc, but this will allow us to hide details
like which backend to use for a specific request, or a caching system.

cff2ba15