James K Nelson

Thanks for getting back to me on this – it really shouldn't be necessary to do it that way. Part of me wonders if maybe you're using mismatching versions of...

Okay, I’ve reopened this. Could someone who is having this issue create a reproduction repo for me to look to? Long term, I think the best solution is going to...

One possibility would be to put the user details in context, and then use a top-level `map`. Something like this: ```js mount({ '/change-password': lazy(() => import('./change-password')), '*': map(request => {...

@JacksonGariety that sounds like an interesting solution. Could you explain in a little more detail what `navigation.pause()` would be supposed to do?

The behavior here has changed in 0.13 (which was released a few minutes ago). In 0.12, it *should* have worked automatically, although this prevented people from integrating Navi with react-helmet...

Glad that it works 😆. I'll leave this one open for a little while just in case anyone else runs into the same issue.

@kettanaito the main benefit for setting the title with Navi is that it's just a plain string, and can be accessed anywhere by checking `useCurrentRoute().title`. It also helps for integration...

I agree, although for backwards compatibility at least it needs to be there for now (Navi has rendered page title since it's first release - this is actually the first...

Okay :-) Any ideas on the approach you'd take to putting this together?

Glad to hear that you're enjoying Navi at work :D Where do you think would be a good place to chat? Perhaps I should start a Spectrum?