currently all tours, after finished or skipped, store a value in the LocalStorage under the name of vjs-tour. If this value becomes true then the tour does not start. Which is great so we don't have the tour constantly in popping up.
However, if we have 2 pages and need to have a tour on both pages, then there is no way currently (that I know of) to differentiate these tours.
I think the best solution is to implement a name prop where we can pass a string. This should probably be required to prevent issues with forgetting and having some default through out their application.
In the (Vue Tour)[https://github.com/pulsardev/vue-tour] package, they reference the name to start their tour. We wouldn't need that as we can reference directly
const myTour = ref()
myTour.value.startTour()
So the name could just be for the localStorage.
<VTour ref="myTour" name="uniqueTourName" :steps="steps" />
--- Local Storage
vjs-uniqueTourName | true // After finished.
Or maybe we can just use the ref?
<VTour ref="myTour" :steps="steps" />
--- Local Storage
vjs-myTour | true // After finished.
currently all tours, after finished or skipped, store a value in the LocalStorage under the name of
vjs-tour
. If this value becomestrue
then the tour does not start. Which is great so we don't have the tour constantly in popping up.However, if we have 2 pages and need to have a tour on both pages, then there is no way currently (that I know of) to differentiate these tours.
I think the best solution is to implement a
name
prop where we can pass a string. This should probably be required to prevent issues with forgetting and having some default through out their application.In the (Vue Tour)[https://github.com/pulsardev/vue-tour] package, they reference the name to start their tour. We wouldn't need that as we can reference directly
So the name could just be for the localStorage.
Or maybe we can just use the ref?