Skip to content

Releases: Ferruslogic/PhotonJSON

v1.2.4

06 Mar 14:26
Compare
Choose a tag to compare

Added documentation

PhotonJSON version 1.2.2

12 Jul 00:21
Compare
Choose a tag to compare

Changes in this version

  • Formatted JSON beautiful, now escape quotes inside strings correctly.
  • Added format validation.

v1.2.1

20 Feb 05:58
Compare
Choose a tag to compare

Overwrite default json conversion handlers

PhotonJSON version 1.2.0

20 Jan 15:59
dd113f5
Compare
Choose a tag to compare

Changes in this version

  • When converting a JSON string to a LiveCode array, empty Javascript objects and arrays are no longer converted to plain empty variables. They are now converted to their LiveCode equivalent, so that the type is not lost when converting the LC Array to JSON again.

  • The "" are replaced by null when converting from array to JSON. This is for compatibility with the ECMA-404 standard.

PhotonJSON version 1.1.2

16 Jan 21:16
Compare
Choose a tag to compare

changes in this version

  • Added back the BeautifyJSON function since it was removed in the previous version. Since BeautifyJSON is for formatting an existing JSON string. Returning the formatted string in a prettier and nicer way.

PhotonJSON version 1.1.1

02 Dec 03:33
Compare
Choose a tag to compare

changes in this version

• In this version of the library, functions that were deprecated are removed. Which makes it no longer compatible with LiveCode versions lower than 7. Thanks to @Monox18 for the suggestion
• The functions that were used to detect the encoding of the input string are removed, since this string must be a UTF-8 string.
• The beautifyJSON() function is removed, because with the JSONStringify() function you can format JSON very well.

v1.1.0

22 Jun 17:29
Compare
Choose a tag to compare

• 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

v1.0.4

16 Dec 01:27
Compare
Choose a tag to compare
  • This release fixes the handling of escaped characters. (Thanks to Brian Milby for his great help).
  • the name of the JSON object keys is treated as a string. To follow the ECMA-404 standard. This makes converting an array to JSON a bit slower.

JSON encoding / decoding

14 Dec 20:10
Compare
Choose a tag to compare

LiveCode script library for working with JSON, written in livecode-script and without the use of external.

  • This library follows the ECMA-404 standard