Hi @JohnCoene , there are some instances where it's useful for a guide to be triggered by a Javascript action (such as a module load). However, sometimes altering options on the page causes the UI to render again and trigger the guide again. We currently have a wrapper around the guide$init()$start() call that ensures they only run once. Do you think this might be something worth adding as an option to the init method?
If so, lmk and I can PR, otherwise feel free to close
Hi @JohnCoene , there are some instances where it's useful for a guide to be triggered by a Javascript action (such as a module load). However, sometimes altering options on the page causes the UI to render again and trigger the guide again. We currently have a wrapper around the
guide$init()$start()
call that ensures they only run once. Do you think this might be something worth adding as an option to theinit
method? If so, lmk and I can PR, otherwise feel free to close