Closed slackwareer closed 2 months ago
@slackwareer The behavior is intentional. I only added the request hooks later. I wanted to offer an easy way to change/extend the replaced request again later. The difference between an execute and the request hook is basically the replacement.
The script below contains a global region and a test region(only JavaScript with no request named test-1) . When executing test-1 region , the first global region cannot be executed. An exception will be raised during exec of the test-1 region.
But when the @request is removed, the test-1 regions will run successfully..
Maybe the variable replace hookitem should be moved after the @request region , just before the request execution?