Skip to content

Releases: mangiucugna/json_repair

Release 0.17.2

07 May 11:00
Compare
Choose a tag to compare

Fixed

  • Fix #40, in some cases a \ would send the library in an infinite loop. Thanks to @dhrbobluo for reporting!

Release 0.17.1

06 May 11:56
Compare
Choose a tag to compare

Fixed

  • Fix #39, a regression after the large refactor of the string function (done to support new use cases) introduced a bug in which the library would fail in a specific corner case. Thanks to @werpachowski-msft for reporting!

Release 0.17.0

03 May 15:18
Compare
Choose a tag to compare

Added

  • Improve load() to avoid loading the file in memory but stream it byte by byte. This brings the method on parity with json.load() and allows large stream of data to be processed

Release 0.16.3

30 Apr 10:13
Compare
Choose a tag to compare

Fixed

  • Fix #38, the new functions load() and from_file() were not properly exported but pointed to loads(). Thanks to @Jaron123 for reporting!

Release 0.16.2

30 Apr 08:14
Compare
Choose a tag to compare

Fixed

  • Fix #37, the parser was wrongly allowing an object key to be any type but that should be only string type. This is fixed now. Thanks to @liangjs for reporting

Release 0.16.1

30 Apr 06:17
Compare
Choose a tag to compare

Fixed

  • Fix #36, a simple case of a missing comma in a simple object wasn't handled correctly, still a regression from 0.14.0. Thanks @liangjs for reporting the issue!

Release 0.16.0

29 Apr 18:28
Compare
Choose a tag to compare

Added

  • Better handling of stray characters. Before this version, stray characters at the beginning of a valid json ( e.g. string { 'a': 'b'} ) would not be ignored and the json produced would be invalid. Thanks to @lujasmine for reporting the issue

Release 0.15.6

29 Apr 14:58
Compare
Choose a tag to compare

Fixed

  • Fixed #33, the feature released in 0.14.0 had a number of unexpected side effects. This should provide a more general and stable fix.

Sorry for any inconvenience, please keep sending examples as this specific feature is really at the core of a bunch of different failure modes

Thanks to @dcollien for reporting.

0.15.5

28 Apr 13:23
Compare
Choose a tag to compare

Fixed

  • A more stable and general fix to the bug fixed in 0.15.5

Release 0.15.4

28 Apr 04:59
Compare
Choose a tag to compare

Fixed

  • Fix #32, an empty object value ("") would cause a crash under certain conditions. Thanks to @liangjs for reporting the issue!