From abc387ac3cb2cd5c7b91c426f9f9d5313e6dd668 Mon Sep 17 00:00:00 2001 From: gnezim Date: Sat, 18 Apr 2026 13:47:19 +0300 Subject: [PATCH] Omit blank departure/arrival in schedule details request MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Upstream returned HTTP 400 for empty departure/arrival values. Angular derives them from per-leg data when missing; easier fix here is to simply not send them — the backend accepts the request without those query params. --- src/features/schedule/api.ts | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/src/features/schedule/api.ts b/src/features/schedule/api.ts index bc33e890..068ca069 100644 --- a/src/features/schedule/api.ts +++ b/src/features/schedule/api.ts @@ -79,10 +79,13 @@ export async function getScheduleDetails( arrival: string; }, ): Promise { - const query: Record = { - departure: params.departure, - arrival: params.arrival, - }; + // Omit blank departure/arrival so the upstream doesn't reject the + // request. Angular's details-data-source.service falls back to + // per-leg values when the page-level params are missing; the + // backend accepts the request either way. + const query: Record = {}; + if (params.departure) query["departure"] = params.departure; + if (params.arrival) query["arrival"] = params.arrival; for (let i = 0; i < params.flights.length; i++) { const flight = params.flights[i];