Skip to content

v1.1.0

Compare
Choose a tag to compare
@torocruzand torocruzand released this 22 Jun 17:29
· 46 commits to main since this release

• When the JSON had a key with a value of {} or [], as a key value. Much of the information that followed this statement was lost or corrected.
• Both in the process of converting a JSON into an Array and in converting an Array into a JSON. The caseSensitive is on. It is to prevent information from being lost. Because if I have two keys called "A700" and "a700". One will overwrite the other, regardless of whether the value of the two is different
• To comply with the ECMA-404 standard in a more rigorous way, the algorithm used to convert an array into JSON is rewritten
• Some parameters in the functions have been changed so that there is better compatibility with projects that use MegeJSON
• All functions that expect a JSON string, expect it to be UTF-8
• All functions that return a JSON string, return it encoded in UTF-8
• Fixed the error that occurred when converting an array to JSON with a nice format. This error that replaced new lines with \\n instead of \n