JSON parameters are always strings

[mlongbrake]

When using the new JSON request body type it seems like all parameters are assumed to be strings. If I type false to make a boolean value it ends up with quotes around it. Same thing with an integer. The user should be responsible for quoting things that are strings.

[eliihen]

Hi,

Yes, this is an issue. I guess we could try an eval on the value to see if it is parseable to any other type, then fall back to the value as a string if that fails. This would mean if you wanted the string true, you would need to type 'true', whereas the string foo would simply need foo without any quotes. Inconsistent, but possibly closer to expected behavior.

[eliihen]

All JSON values are now parsed with JSON.parse, meaning that numbers, booleans and objects (recursively) are all supported. If you for example need to use the string true, you need to use a JSON string format, which is "true" to escape the parsing.

Pushed on the next branch, will be part of 2.2.0. Thanks for the suggestion.