Per discussion on MW.org, +1. The method's been "deprecated" for almost a decade without being removed and there'd be a real use case for it, so let's simply revert that part of rEGTOfc9de92a6ae6: Refactor and add non-linear tours, with tests.

I'm not sure if much people will see this though, the last tasks I've created got no response. I may have to learn how to fix back myself.

I'm inclined towards just doing this, because the deprecation happened so long ago. But, I'm unsure why it is needed. On a first check, both gt.defineTour and an object-driven approach of Step can be used to create the same GuidedTour? Is there a specific example in which gt.defineTour would be more appropriate (or the only such solution)?

It’s useful when you have a mostly linear tour and want to chain them together. With defineTour, you can chain steps like an array. Otherwise, you have to add names, .next(<name>) and .back(<name>) for every single tour.Step .

Also, after undeprecating we still have to

fix the functionality of the "back" action
Maybe also make it return a TourBuilder object or even make it a TourBuilder constructor

Hey @Urbanecm_WMF , is there any progress on this?

In T350549#9335985, @aliu wrote:

Hey @Urbanecm_WMF , is there any progress on this?

Hello, none that would not be recorded on the task :-). Thanks for the clarification from the other day. I think we'd be fine with that change being made, but unfortunately, we currently do not have the capacity to actually create the patch. If you do, please feel free to upload a patch!

Change #1028874 had a related patch set uploaded (by Pppery; author: Pppery):

[mediawiki/extensions/GuidedTour@master] De-deprecate gt.defineTour

https://gerrit.wikimedia.org/r/1028874

Change #1028874 merged by jenkins-bot:

[mediawiki/extensions/GuidedTour@master] De-deprecate gt.defineTour

https://gerrit.wikimedia.org/r/1028874