PrivateCoffee/travelynx
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

handle ambiguous train numbers when requesting train details

Browse source
This commit is contained in:
Daniel Friesel 2019-07-14 17:17:44 +02:00
parent 8e5a8fad93
commit b08b0fb921
1 changed files with 10 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
lib/Travelynx.pm
View file

@ -1763,10 +1763,18 @@ sub startup {
if ( $suggestion->{depDate} eq $date_yy if ( $suggestion->{depDate} eq $date_yy
or $suggestion->{depDate} eq $date_yyyy ) or $suggestion->{depDate} eq $date_yyyy )
{ {
# Train numbers are not unique, e.g. IC 149 refers both to the
# InterCity service Amsterdam -> Berlin and to the InterCity service
# Koebenhavns Lufthavn st -> Aarhus. One workaround is making
# requests with the stationFilter=80 parameter. Checking the origin
# station seems to be the more generic solution, so we do that
# instead.
if ( $suggestion->{dep} eq $train->origin ) {
$trainlink = $suggestion->{trainLink}; $trainlink = $suggestion->{trainLink};
last; last;
} }
} }
}
if ( not $trainlink ) { if ( not $trainlink ) {
$self->app->log->debug("trainlink not found"); $self->app->log->debug("trainlink not found");