Skip to content

Conversation

flibbertigibbet
Copy link
Contributor

Closes #499.

Stores user-added waypoints (modified places on an edited route) in local storage.
Puts waypoints in the URL also. Cleared on origin or destination change,
or other events that cause all itineraries to be cleared from the map.

To test, edit a route. New waypoints should be set in local storage and in URL; edited route should be preserved on page refresh. Shortened link URL should contain intermediatePlaces parameter.

Does not yet preserve previously edited waypoints on subsequent route edits, as we will need to implement #502 to be able to easily get the ordering right.

Do not reverse waypoints when arriveBy is true.
(Done in attempt to address broken results when arriveBy is true and transit mode not selected.
Closes azavea#499.
Stores user-added waypoints (modified places on an edited route) in local storage.
Puts waypoints in the URL also. Cleared on origin or destination change,
or other events that cause all itineraries to be cleared from the map.
@sharph
Copy link
Contributor

sharph commented Sep 28, 2016

build again

@KlaasH
Copy link
Contributor

KlaasH commented Sep 29, 2016

Looks good 👍

@flibbertigibbet flibbertigibbet merged commit 8f5b48a into azavea:redesign Sep 29, 2016
@flibbertigibbet flibbertigibbet deleted the feature/store-waypoints branch September 29, 2016 14:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants