-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DT-6533 Improved navigator and local storage cooperation #5162
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that when you open itinerary detaul view of a bike and transit itinerary, hash is not itinerary index. It can be found from secondaryHash.
As far as I can see, we need to 'auto relaunch' navigation only in one occasion: page reloading. This is handled in useEffect [].
Will refactor with this in mind. For possible future reference the current implementation enables the user to browse between itineraries and their detail views. Browsing to the exact same search result auto-launches Navigator. Only explicit backtrack from an initiated journey or a change in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
very good
Proposed Changes
Navigator is now more context aware:
from
,to
,time
,arriveBy
andhash
parameters are identical to those of the stored journeyItineraryPage
detail view will automatically trigger the Navigator journey.from
,to
,time
andarriveBy
parameters are identical to those of the stored journeyItineraryPage
list view does not necessarily purge the stored itinerary from memory.ItineraryPage
detail view does not purge the stored itinerary from memory, but a Navigator journey is not triggeredItineraryPage
list view or detail view will purge the stored Navigator journey from local storagePull Request Check List
Review