Active EASDK nagivation link doesn't change

Solved
Highlighted
Shopify Partner
27 1 4

I'm setting up the EASDK navigation extension with my app.

 

https://help.shopify.com/en/api/embedded-apps/app-extensions/navigation/create-navigation-link

 

Everything is working, except that the active link style doesn't change when I navigate between pages (the first link in the navigation is always highlighted). How is this supposed to work?

1 Like
Highlighted
Shopify Partner
27 1 4

This issue is holding up our next app release, so I'd really appreciate some insight. Thanks!

0 Likes
Highlighted
Shopify Staff
Shopify Staff
1555 81 282

This is an accepted solution.

The navigation links only match the beginnings of the paths, and they're only checked and updated if you use App Bridge navigation actions to wire them together, which might explain what you're seeing. In the mean time, I'm going to look into documenting this when I get some cycles.

 

That said, we're working on improving this experience in the future.

0 Likes
Highlighted
Shopify Partner
27 1 4

Thanks @Alex for your reply. Turns out it was because my main page was /app, and the other links were all under /app/*, so because it only checks the beginning of the path, I guess it just stopped at the first match. That doesn't seem ideal, but I guess at least if it is documented behaviour, it should be okay.

1 Like
Highlighted

Hi, is there any development on this. I believe current solution is sub-optimal.

 

EDIT: Let me elaborate on that. We're currently using TitleBar as a place to display our navigation. We're trying to migrate from Polaris 2.12 to current version. This involves switching to Shopify App Bridge. However the upgrade is causing the TitleBar to refresh(meaning it hides and the shows). Please see following video describing the issue. https://www.loom.com/share/a4c86f9b3cce4699bcf2ee461a4910b2

 

Our URL scheme is following:
/dashboard/
/dashboard/settings
/dashboard/analytics

/dashboard/faq

 

It would be very hard to switch our URL scheme because of the framework, we're using.

0 Likes