Calling setEnvVar without converting response value to string results in crash when configuring environment

[bjornevik]

Version: 1.0.0

A "crash" seems to be caused when using setEnvVar to set an environment variable to a response value which is not a string. This only seems to happen when setting equal to a value from the response. If using setEnvVar("value", 123456789) directly it works fine, but if 123456789 is part of the response-object it seems to not handle it correctly.

Example

Given the following response from an API:

{
  "value": 123456789,
}

The following script will cause a crash when clicking to configure environment:

const body = res.getBody()
bru.setEnvVar("value", body.value);

The following script will fill in the value as expected:

const body = res.getBody();
bru.setEnvVar("value", `${body.value}`)

Screenshots

With following postscript:

After running query:

Results in:

[helloanoop]

@bjornevik Usually strings are expected to be store in thesetEnvVar.
We should be able to fix this by doing a JSON.stringify() before saving and JSON.parse() before fetching

I need to think about this to see if there will be any effects.

Meanwhile, Can you use bru.setVar('key', val) and bru.getVar('name')
This allows storing full objects as well as exploring them in the Variable Viewer

[bjornevik]

Ah! I didn't realize that there was a separate collection variables tab, it seems more inline with most of my use cases. Thanks :D

[bjornevik]

Seems like this was fixed in #1285