I think you just need the equivalent of a custom component (like react-router's <Link />) or attribute (like angular UI-router's ui-sref) that uses html5 pushState for all the routing. That is the modern, standards-compliant way to do SPA routing. I would strongly caution anyone against using hash fragment based routing.
I'd be surprised to find out there isn't already a solution in the package repository, but if there isn't then it should still be easy to create a function that wraps the content in an <a> tag with a proper custom handler that sends a message and causes a history.pushState for all route transitions. On Fri, Dec 16, 2016 at 9:47 AM Bob Hutchison <[email protected]> wrote: > Hi, > > > Navigate to http://localhost:8080*/#test?a=b&c=d* > > > What happens if you write it according to ( > https://tools.ietf.org/html/rfc3986#section-4.1): > > http://localhost:8080*/?a=b&c=d**#test* > > -- > 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 [email protected]. > For more options, visit https://groups.google.com/d/optout. > > -- > 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 [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
