-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Closed as not planned
Closed as not planned
Copy link
Labels
!BugApply to issues describing a bug and PRs witch fixes it.Apply to issues describing a bug and PRs witch fixes it.EnturOn Entur RoadmapOn Entur RoadmapStaleThis issue is stale, no activity for 90 days. Remove stale label or comment within 30 days.This issue is stale, no activity for 90 days. Remove stale label or comment within 30 days.
Milestone
Description
This bug apply to the Transmodel API and the estimatedCalls query. This query was probably not changed when the destination display via functionality was added.
Expected behavior
The following query return only one result, even if there is 2 distinct DestinationDisplay entries.
Query
{
stopPlaces(
ids: "NSR:StopPlace:41294"
) {
id
quays(
filterByInUse: true
) {
id
estimatedCalls(
startTime: "2023-12-07T10:20:00",
timeRange: 86400,
numberOfDeparturesPerLineAndDestinationDisplay: 1,
numberOfDepartures: 70,
arrivalDeparture: departures,
includeCancelledTrips: true,
whiteListed: {
lines: "MOR:Line:701"
}
) {
realtime
destinationDisplay {
frontText
via
}
}
}
}
}
If we change to numberOfDeparturesPerLineAndDestinationDisplay: 2, then we get the expected entries.
Version of OTP used
dev-2.x
Data sets in use
Latest ENTUR
Metadata
Metadata
Assignees
Labels
!BugApply to issues describing a bug and PRs witch fixes it.Apply to issues describing a bug and PRs witch fixes it.EnturOn Entur RoadmapOn Entur RoadmapStaleThis issue is stale, no activity for 90 days. Remove stale label or comment within 30 days.This issue is stale, no activity for 90 days. Remove stale label or comment within 30 days.