Boolean values in JSON get improperly "stringified"

[thomgre]

I've noticed that specifying an unquoted boolean value for a JSON file property will result in an incorrect value. For example:

Target file:

{
  "UseMySetting": false
}

Magic-chunks transformation (expected result):

{
  "UseMySetting": true
}

Actual:

{
  "UseMySetting": "True"
}

This will result in a valid JSON file but is not the expected end result with a correct JSON boolean value.

[TLA020]

I'm dealing with that same problem.

[bh3605]

This issue needs more attention.

[XVCoder]

Same problem. 😭

[thomgre]

I'd suggest to use the ReplaceTokens task from colindembovsky instead.