Step ID is created with the route the component is initialized on about ngx-joyride HOT 5 CLOSED

Hi @tb9-Mason ,
When you say that sometimes the step would show and sometimes not, you are navigating your app in a different order for the two cases, right? Is it your step on the root route?

Lets suppose you have 2 routes: routeA and routeB:
What you're saying is that its behaviour is chameleonic, sometimes it is initalized with routeA and sometimes with routeB, depending on which page is loaded first, is it right?

I'll have a look on this. Anyway, maybe the cleanest solution could be use the stepName as ID, without the route; in this way the stepName should be unique across all the app routes.

from ngx-joyride.

@tnicola Thanks for your quick reply
I am not navigating in a different order, but sometimes I was refreshing the app on the route that generated the correct ID and sometimes I was not.

In my case, the main app template where my step is located is always in a sub route of the application. You are correct in that sometimes the step ID is created as myStep@routeA and sometimes as myStep@routeB, but in the steps passed to startTour the name is always myStep@routeA.

from ngx-joyride.

Alright then, I'll try to reproduce it and i will fix it in the next days!

from ngx-joyride.

Hi @tb9-Mason ,
This issue should be fixed in the latest version 2.0.2. I removed the name + route check, now the lookup is only on the name. Let me know if it works.

from ngx-joyride.

Closing the issue.

from ngx-joyride.