Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pending discussion in #60, just the simple switch to the
db-vendo-client
backend, without any documentation changes yet.I have verified that caching* and the basic API works as expected – and I've been using
hafas-rest-client
together withdb-vendo-client
for multiple weeks now, so that part should be fine. (I have smuggled in backwards-compatible support for multiple travellers, sincedb-vendo-client
supports that now).EDIT: Caching never worked even for quickly repeated requests of e.g. boards without a
when
param and the same (default) duration, since it would assume that within these few seconds, a new departure/arrival could be inside the window.Before releasing/deploying a new version of db-rest, it may also be useful to discuss these PR's in upstream projects:
public-transport/hafas-rest-api#15
derhuerst/db-hafas-stations#3