[BUG] JSON formatter fails to handle non-string variable placeholder

[the8tre]

When trying to assign a non-string value from the collection/environment to a JSON field the formatter reports a parsing error:
Expecting 'STRING' , '}' got '{'
Sample valid JSON:

{
  "SomeField": 42
}

Sample failing JSON:

{
  "SomeField": {{someVar}}
}

Tested in Bruno 1.2.0

[n00o]

You have to put collection/environment variables inside of a string for it to work. So it would look like something like this:

{
  "SomeField": "{{someVar}}"
}

It's understandably confusing since the text turns orange implying that it is correctly formatted. I guess it could be possible to interpolate collection/environment variables outside of quotes if they are numbers but it would be programmatically complicated. The other solution would be to provide a hint that it needs to be inside of a string to work.

[the8tre]

I get the idea of wrapping things as strings.
But this will lead to a 400 error if the API being called expects a number or a boolean instead of a string.

I agree that dispite the error in the editor (without string wrapping) the call will still work, but the the prettifier can't prettify anymore.

[n00o]

This relates to the pull request I made here #1025. I can make sure the JSON linting errors doesn't show for Bruno collection/environment variables.

[n00o]

It appears that the Prettify button for JSON bodies doesn't work anymore if you use {{someVar}} in the without quotes inside of it. Might need to fix that too.

[n00o]

This issue can be closed now @helloanoop. Didn't realize there was keywords like closes that could be added to pull requests to connect them to issues. Will make sure to add that to future requests.