Here is some code to make things more concrete https://gist.github.com/simonh1000/9368f9dbd7f93646207ec27fdf3662a2
It is based on the example from the Navigation library, but with the links changed from # to (I think they are called) HTML5 links. I added an onClick handler to provide a preventDefault as otherwise the links 404, but with this handler the links don’t navigate instead The aim is to get the navigation history ticking along properly without page refreshes. I know its possible as I’ve seen it in other routers Simon On Saturday, 26 November 2016 13:44:20 UTC+1, Wouter In t Velt wrote: Thank you for the explanation Erik! With the upgrade to 0.18 and the > changes in navigation, I was wondering which route (pun intended) to follow > with the upgrade. Not sure I follow completely though. > > In option 1, could you deal with redirect-like scenario's inside the SPA? > Like > > 1. user is on the "/apples" page, showing all available apples. > 2. user types "/apples/234" in the url-bar > 3. there happens to be no such apple > 4. I want the user to stay on the "/apples" page, and get a message > like "this apple is forbidden fruit" > 5. at this point, I would want the url-bar to also say "/apples" > > Can this work with option 1? Or is this only possible with option 2? > -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
