json-repair 0.10.0__tar.gz → 0.10.1__tar.gz

{json_repair-0.10.0/src/json_repair.egg-info → json_repair-0.10.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: json_repair
-Version: 0.10.0
+Version: 0.10.1
 Summary: A package to repair broken json strings
 Author-email: Stefano Baccianella <4247706+mangiucugna@users.noreply.github.com>
 License: MIT License
@@ -56,20 +56,20 @@ I searched for a lightweight python package that was able to reliably fix this p
 You can use this library to completely replace `json.loads()`:
 
     import json_repair
-    
+
     decoded_object = json_repair.loads(json_string)
 
 or just
 
     import json_repair
-    
+
     decoded_object = json_repair.repair_json(json_string, return_objects=True)
-    
+
 ### Performance considerations
 If you find this library too slow because is using `json.loads()` you can skip that by passing `skip_json_loads=True` to `repair_json`. Like:
 
     from json_repair import repair_json
-    
+
     good_json_string = repair_json(bad_json_string, skip_json_loads=True)
 
 I made a choice of not using any fast json library to avoid having any external dependency, so that anybody can use it regardless of their stack.
@@ -77,7 +77,7 @@ I made a choice of not using any fast json library to avoid having any external
 Some rules of thumb to use:
 - Setting `return_objects=True` will always be faster because the parser returns an object already and it doesn't have serialize that object to JSON
 - `skip_json_loads` is faster only if you 100% know that the string is not a valid JSON
-
+- If you are having issues with escaping pass the string as **raw** string like: `r"string with escaping\""`
 ## Adding to requirements
 **Please pin this library only on the major version!**
 

{json_repair-0.10.0 → json_repair-0.10.1}/README.md

@@ -19,20 +19,20 @@ I searched for a lightweight python package that was able to reliably fix this p
 You can use this library to completely replace `json.loads()`:
 
     import json_repair
-    
+
     decoded_object = json_repair.loads(json_string)
 
 or just
 
     import json_repair
-    
+
     decoded_object = json_repair.repair_json(json_string, return_objects=True)
-    
+
 ### Performance considerations
 If you find this library too slow because is using `json.loads()` you can skip that by passing `skip_json_loads=True` to `repair_json`. Like:
 
     from json_repair import repair_json
-    
+
     good_json_string = repair_json(bad_json_string, skip_json_loads=True)
 
 I made a choice of not using any fast json library to avoid having any external dependency, so that anybody can use it regardless of their stack.
@@ -40,7 +40,7 @@ I made a choice of not using any fast json library to avoid having any external
 Some rules of thumb to use:
 - Setting `return_objects=True` will always be faster because the parser returns an object already and it doesn't have serialize that object to JSON
 - `skip_json_loads` is faster only if you 100% know that the string is not a valid JSON
-
+- If you are having issues with escaping pass the string as **raw** string like: `r"string with escaping\""`
 ## Adding to requirements
 **Please pin this library only on the major version!**
 

{json_repair-0.10.0 → json_repair-0.10.1}/pyproject.toml

@@ -3,7 +3,7 @@ requires = ["setuptools>=61.0"]
 build-backend = "setuptools.build_meta"
 [project]
 name = "json_repair"
-version = "0.10.0"
+version = "0.10.1"
 license = {file = "LICENSE"}
 authors = [
   { name="Stefano Baccianella", email="4247706+mangiucugna@users.noreply.github.com" },

{json_repair-0.10.0 → json_repair-0.10.1}/src/json_repair/json_repair.py

@@ -209,9 +209,13 @@ class JSONParser:
                     break
             self.index += 1
             char = self.get_char_at()
+            # If the string contains escaped delimiters we should respect that
+            if char == rstring_delimiter and self.get_char_at(-1) == "\\":
+                self.index += 1
+                char = self.get_char_at()
             # ChatGPT sometimes forget to quote links in markdown like: { "content": "[LINK]("https://google.com")" }
             if (
-                (char == lstring_delimiter or char == rstring_delimiter)
+                char == rstring_delimiter
                 # Next character is not a comma
                 and self.get_char_at(1) != ","
                 and (

{json_repair-0.10.0 → json_repair-0.10.1/src/json_repair.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: json_repair
-Version: 0.10.0
+Version: 0.10.1
 Summary: A package to repair broken json strings
 Author-email: Stefano Baccianella <4247706+mangiucugna@users.noreply.github.com>
 License: MIT License
@@ -56,20 +56,20 @@ I searched for a lightweight python package that was able to reliably fix this p
 You can use this library to completely replace `json.loads()`:
 
     import json_repair
-    
+
     decoded_object = json_repair.loads(json_string)
 
 or just
 
     import json_repair
-    
+
     decoded_object = json_repair.repair_json(json_string, return_objects=True)
-    
+
 ### Performance considerations
 If you find this library too slow because is using `json.loads()` you can skip that by passing `skip_json_loads=True` to `repair_json`. Like:
 
     from json_repair import repair_json
-    
+
     good_json_string = repair_json(bad_json_string, skip_json_loads=True)
 
 I made a choice of not using any fast json library to avoid having any external dependency, so that anybody can use it regardless of their stack.
@@ -77,7 +77,7 @@ I made a choice of not using any fast json library to avoid having any external
 Some rules of thumb to use:
 - Setting `return_objects=True` will always be faster because the parser returns an object already and it doesn't have serialize that object to JSON
 - `skip_json_loads` is faster only if you 100% know that the string is not a valid JSON
-
+- If you are having issues with escaping pass the string as **raw** string like: `r"string with escaping\""`
 ## Adding to requirements
 **Please pin this library only on the major version!**
 

{json_repair-0.10.0 → json_repair-0.10.1}/tests/test_json_repair.py

@@ -103,6 +103,7 @@ def test_repair_json():
                        { "key": "value" }
                        ```""") == '{"key": "value"}'
     assert repair_json('````{ "key": "value" }```') == '{"key": "value"}'
+    assert repair_json(r'{"real_content": "Some string: Some other string Some string <a href=\"https://domain.com\">Some link</a>"') == r'{"real_content": "Some string: Some other string Some string <a href=\\\"https://domain.com\\\">Some link</a>"}'
 
 
 

{json_repair-0.10.0 → json_repair-0.10.1}/tests/test_performance.py

@@ -580,7 +580,7 @@ def test_true_false_correct(benchmark):
   mean_time = benchmark.stats.get("median")
 
   # Define your time threshold in seconds
-  max_time = 22 * (1 / 10 ** 6)  # 21 microsecond
+  max_time = 23 * (1 / 10 ** 6)  # 23 microsecond
 
   # Assert that the average time is below the threshold
   assert mean_time < max_time, f"Benchmark exceeded threshold: {mean_time:.3f}s > {max_time:.3f}s"
@@ -624,7 +624,7 @@ def test_false_false_correct(benchmark):
   mean_time = benchmark.stats.get("median")
 
   # Define your time threshold in seconds
-  max_time = 55 / 10 ** 6  # 55 microsecond
+  max_time = 56 / 10 ** 6  # 56 microsecond
 
   # Assert that the average time is below the threshold
   assert mean_time < max_time, f"Benchmark exceeded threshold: {mean_time:.3f}s > {max_time:.3f}s"