Converter not returning the correct route about navi HOT 5 CLOSED

The pathname: '/wp' param did the trick, thank you for that! After getting that /wp portion solved, I ran into the same exact problem right away though, where routes that I defined under next properties of top-level routes were not coming through in the route object.

But after looking at your "Base Location" example on this line I realized that I needed to explicitly pass the route.next junction as well as the locate function to my child components from my AppScreen component.

Once I figured that out, everything magically worked!

from navi.

I think what is happening is that your switch statement is switching over the wp route instead of the inner route. You can confirm this by printing the route to screen.

That said, if your application lives underneath a subdirectory, it is probably best to use the baseLocation path feature of the Converter class.

To do this, change the createConverter call to:

createConverter(AppScreen.junction, { pathname: '/wp' })

You'd also want to remove the wp junction and just use the inner junction that you have.

Let me know if this works!

from navi.

Another thing I'm noticing is that a full page reload occurs when I click between links to go to different locations that I'm using the <Link> component from react-junctions to produce. Anyway to prevent that?

from navi.

You may need to pass a history to your <Link> components, either with props, or with a HistoryContext.

from navi.

👍 That was it! Thanks! Good to see how these pieces fit together outside of using components that pass this all down with React context.

from navi.