Optimize Itinerary page rendering for geolocated routes

Description

Currently there occurs 3 rendering cycles:

1. Server side rendered page which fails due to references to client location
2. New render after the user has been geolocated
3. New render after the itineraries have been found

Server side rendering should detect 'POS' reference in URL and render something appropriate. Optimally, there will be a single loading screen which changes to finished content after the ininerary search is ready.

Acceptance Criteria

None

Assignee

Unassigned

Reporter

Vesa Meskanen

More details from

None

Components

Priority

Medium

Epic Link

Story Points

None

Labels

None
Configure