Like ui-router, but without all the Angular. The best way to structure a single-page webapp.
1 second
For any state that you want to be preserved when the user refreshes the page, or in the browser history, you call
stateRouter.go (or have the user click on a link) to update the url with any parameters representing what has changed, which will cause the necessary components to update
so, in that case, you can make that work
you can set up the
activate function for that state, and have it listen for events
That's obviously a BS demo "login" there, but you can do whatever server-touching requests in there
I would have thought I could fire my normal Svelte events and then hook into those at a parent level
or even global level
I feel so dumb right now
as in the
asr.makePath
a really good helper
said another way: that function is the canonical way to build a URL to navigate around your ASR-routed app
I usually have two kinds of components in apps like this
the ones that are the actual state templates, that are mounted directly by ASR. These are ASR-aware, and more tied in to the rest of the application. They contain other components which don't directly access ASR, and are more simple view components that emit events
I have learnt so much from this
Thanks for all the info you all provided
Not at all, but its just a finding I wasn't aware of
for instance, that would make a good candidate for logout
But hoisting would kill it
So i guess not
For logging out, I prefer having a "logout" state that talks to the server in its
resolve
So you make the logout happen with
state.go('logout') or having the user click on a link <a href="{{ asr.makePath('logout') }}">logout</a>