>I would understand the >declaration of a general variable, but (at the moment) not a special >regex one
See https://jmeter.apache.org/usermanual/component_reference.html#Regular_Expression_Extractor Regular expression extractor sets and resets **several** variables. I think variable names like refName_gn, refName_n_gm, refName_matchNr are not really accessible, and regular-expression-related holders would help to hide _n_gm names. There might be a case for val upperName by variables.javaScript("$name.toUpperCase()") that translates to UserDefinedVariables(name: upperName, value: ${__javaScript(getVar("nameVar").upperCase())}) >I think same feature (#toString) can be used to >introduce JMeter functions Exactly. Something like `if`(javaScript("2+2")) {...} could render to IfController with the condition of ${__javaScript(2+2)} >With respect to naming `extractRegex`: I suggest we try something first and then figure out if there's a common ground. The key difference between extractByRegex {...} and extractor(regex) { ... } is that in the first case, the lambda is always typed as "regex extractor". In the second case, the type of lambda depends on the type of argument. It might be possible with a few generics, however, in theory, it is a more complicated design. Vladimir
