Feature/add execution context

[tlaloc911]

Description

In reference to #1874
I have the need to know the execution context of the request:

1. Name of the Request executed
2. Path of the .bru name
3. Execution mode: single, runner, cli
4. Associated documentation of the request

This will allow me to take some decisions in scripts, such as how to name logs, where to find data associated to every request, apply or exclude some tests depending on the way it is launched, etc.

Pre Request script example

console.log("-------- executionMode ----------")
console.log(bru.getVar("executionMode"))
console.log("-------- pathname ----------")
console.log(bru.getVar("currentItem").pathname)
console.log("-------- filename ----------")
console.log(bru.getVar("currentItem").filename)

Outputs

Contribution Checklist:

• The pull request only addresses one issue or adds one feature.
• The pull request does not introduce any breaking changes
• I have added screenshots or gifs to help explain the change if applicable.
• I have read the contribution guidelines.
• Create an issue and link to the pull request.

Note: Keeping the PR small and focused helps make it easier to review and merge. If you have multiple changes you want to make, please consider submitting them as separate pull requests.

Publishing to New Package Managers

Please see here for more information.

[mjhcorporate]

Interesting idea! But I worry about potential name-conflicts with user-defined variables.

How about attaching this info to the bru object? Something like

bru.context.executionMode
bru.context.currentItem

In Postman, there was pm.request.name for the currentItem.fileName...

[tlaloc911]

hi @mjhcorporate, in fact, I wanted to include it in the request object, but I notice the req object is different depending on the context: single request, runner or cli and I prefer not to touch it because it can break somenone's script

[mjhcorporate]

Yes, I agree that we should not put it on the request object, and that we should not break existing scripts. I think attaching new properties to the bru object is the safest path forward.

[tlaloc911]

This was partially solved by #3105, and I open #3298 implementing the filepath part