Tobias Davis

The second test that I added, I believe it should be passing as-is. If I added a console log at the top of each resolve, like `console.log(resolvedCount, stateName, params)` then...

Suppose that I'm at a state like `app.schoolId.teams.list.published` and something I do changes the `school` object which is loaded in the `resolve` of `app.schoolId`. I _think_ I would like to...

That's essentially what I'm starting to work toward as well. Getting it started has felt kind of clunky, but it's pretty clear that after I make a handful, some obvious...

I started developing my tooling for this using [this emitter](https://github.com/TehShrike/better-emitter). There's a little work with making sure to unsubscribe the emitter when a component is destroyed, etc., but it's been...

@sw-clough This might not work for you, but I'll show you one of the ways that I manage updates. I leave it here in hopes that it helps you, or...

Once the other PRs are settled, I'll come make sure this is updated and still works. Anyone feel free to ping me if I get distracted. 😅

That sounds like opt-in behaviour, so I guess it wouldn't be too bad, but it sounds a bit more application specific than I'd like in an abstract router, especially since...

One limitation I do note, is that `stateError` and `stateChangeError` don't currently pass along `lastCompletelyLoadedState` or `lastStateStartedActivating`, and I could definitely see that being useful information to have. Maybe changing...

Since maybe people will search for this and wonder, here's basically what I've done in a few apps: ```js const shouldScrollToTop = (currentState, previousState) => { return currentState === 'some...

Oooh, fancy!