Peter Thomas

tagging as help wanted, I think you have enough context so you can attempt a PR

@edwardsph @joelpramos just realized a complication. what if there is a `Background`. so here is what I propose: ```cucumber Feature: Background: * print 'in background' @setup Scenario: * def data...

cc @ericdriggs for thoughts since I remember you have a lot of complex "setup" flows

another advantage of this system, it encourages re-use of data setup functions within any feature. so the very first example in this thread becomes: ```cucumber Feature: @setup Scenario: * def...

another reason why the `Background` should NOT run for a `@setup` is clear. because `setup()` can be called *from* a `Background` ! another question can be should this support a...

@joelpramos okay, I'll try the `@setup=name` idea. I am against `callonce` because I think the workaround mentioned earlier is reasonable, and just to reduce the API learning curve

yes what @edwardsph said. to be honest troubleshooting `callonce` issues is not fun. propose I get the basic flow working, then consider which reminds me @joelpramos maybe we should release...

work in progress, pasting a particularly interesting example of before and after * functions can be used at the point of calling `karate.setup()` * user has to choose which variable...

@joelpramos no, the design is that a setup only returns data. once a outline "row" fires, the variables will be available as `__row` etc. in the `Background` - but I...

@joelpramos yes, I still need to write the docs for this and change existing docs. one thing I was able to validate, see screenshot below. so even in cases where...