Updated: Comment #0
Suggested commit message
Issue #1918768 by larowlan, tim.plunkett, chx: Refactor tour module to use routes instead of paths.
Tour module relies on paths to decide when to display each tour.
In the new world order we should be using route names.
Switch out paths for route names
User interface changes
Change to tour yml format
Original report by @username
Over inwe need config entity queries where we can do path matching, this patch provides pattern matching on single value properties.
Would also nice to be able to have pattern matching on array properties too (tour config entity has a path array property on the entity and contains wildcards - ala the 'pages' textarea on the block placement configuration form).
Here's an example patch cobbled together after conversations with @chx.
Commit credit for @chx too as he rightly pointed out that I should be using preq_quote() and some inconsistencies in my tests.