You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A sophisticated solution would be to "re-compute" duration once the departures/arrivals have been fetched from HAFAS. But I think a simpler solution would be sufficient: If opt.duration is missing, cache the results as an atom.
The text was updated successfully, but these errors were encountered:
Currently, we incorrectly try to cache a
departures()
/arrivals()
call as a collection, even if it has noopt.duration
. In this case,duration
isNaN
.cached-hafas-client/index.js
Lines 196 to 197 in a9e7813
A sophisticated solution would be to "re-compute"
duration
once the departures/arrivals have been fetched from HAFAS. But I think a simpler solution would be sufficient: Ifopt.duration
is missing, cache the results as an atom.The text was updated successfully, but these errors were encountered: