Problem was exposed once the stream controls were wired up:
Using updateUrl() works well on the location page, it's confusing to use the location stream controls on the map page, since every time you select a new location it takes you to the locations page. I think the intended behavior would be to keep the user on the map page and instead update the map location.
I think the best fix would be to get rid of the location page and change the map route so that we store the location code in the url, something like /map?locationCode=:location_code. That way people can book mark map locations as well, which is something Brett talked about. We can create a separate ticket for updating the map route.
We may also need a url param to set full screen detail mode on or off?
Problem was exposed once the stream controls were wired up:
Using
updateUrl()works well on the location page, it's confusing to use the location stream controls on the map page, since every time you select a new location it takes you to the locations page. I think the intended behavior would be to keep the user on the map page and instead update the map location.I think the best fix would be to get rid of the location page and change the map route so that we store the location code in the url, something like /map?locationCode=:location_code. That way people can book mark map locations as well, which is something Brett talked about. We can create a separate ticket for updating the map route.
We may also need a url param to set full screen detail mode on or off?