Some answers by someone switching from v1

[kevinRoomies]

I'm trying to make my tour go over a menu that is has an absolute positionning but it cannot find it, is this a normal behavior

[elrumordelaluz]

I converted in a discussion. This way you can share all the questions. Keep in mind that would be easier to anyone to help if you share a sandbox with the code you are working on.

Thanks!

[kevinRoomies]

Making a sandbox would take too much time

[elrumordelaluz]

at least a reduced reproduction of the parts that creates issues you need help.

[ArutanSipdrae]

It was another case of the step trying to go to a dom element that isn't in the dom yet and doesn't update after it appearing despite having mutationObservables

[elrumordelaluz]

Oh you are absolutely right!

There are some discussions regarding pre and post action. I didn't included some logic in the new major release because there were lots of use-cases unsolved, like async calls, cancelling, and so on; and the logic started to be complicated.
Still thinking that could fit in future releases, help super welcome!

[elrumordelaluz]

@miko007 please give an eye on this approach using custom/controlled setCurrentStep and currentStep. Note that have to upgrade to @reactour/tour@2.10.2 due to a bug fixed on keyboard navigation.

[miko007]

@elrumordelaluz well this is most likely the most elegant solution. i did not see that this option was available and i do not think anything more is needed in the api.

i would add that there is no need for await here, as the navigate() function returned by useNavigate() does not return a promise.

thank you very much for your support. maybe it should be considered to include this example in the examples section, as i guess more people will find it useful.

[elrumordelaluz]

sure! mind fixing the demo and adding to the readme?

[miko007]

@elrumordelaluz no problemo.

i fully cleaned up the example and provided PR #460