gnezim
b01fc2f0c9
Two bugs prevented the popular-requests click from filling the filter: 1. OnlineBoardFilter seeded its fields from initial* props via useState(...), which only runs once. When a user clicked a popular request the parent pushed ?departure=SVO&arrival=LED into the URL and re-rendered with new initial* props, but the sidebar fields kept their previous empty values. Add an effect that diffs the initial* props against a ref and pushes the changes into local state, matching Angular's ngOnChanges behaviour. 2. CityAutocomplete's selectedCity only looked the value up in cityByCode. Airport codes like SVO aren't cities, so the header code label stayed blank. Fall back to airportByCode → city_code so the top-right code renders as 'MOW' when the input shows 'Шереметьево'. End-to-end behaviour now matches Angular: clicking 'Маршрут: Шереметьево - Санкт-Петербург' on the start page updates the URL, populates 'Шереметьево' / 'Санкт-Петербург' in the inputs, shows 'MOW' / 'LED' codes in the labels.