Open
Description
The parser consumes true and false but then dumps them as 1 and 0.
This is an issue in JSON strings that include both true/false and 1/0 values that are intended to represent different data types (boolean vs. numeric).
Technically this behavior makes sense if your program is fully insulated in AHK, because AHK stores and represents these values the same way internally, but if you're sharing the JSON file with other applications, the distinction between true/false and 1/0 can become meaningful.
The code change made in response to issue #4 is tangentially related.
Metadata
Metadata
Assignees
Labels
No labels