jsoneditor/test
Stephen Thompson 48408f4ded Fix https://github.com/josdejong/jsoneditor/issues/314
The JSON path parsing code assumes that string keys within square brackets in JSON paths will be valid, parseable JSON.

However, the ajv library on which this project depends emits string keys in single quotes.

For example, ajv can emit .foo['bar'], which will ultimately end up with a call to JSON.parse("'bar'"). This causes the "Unexpected token ' in JSON at position 0" error thrown from JSON.parse.

 Since ajv shouldn't need to change and since this utility is gone in the next branch, this fix checks for ajv-formatted string keys and patches them to double-quoted strings before calling JSON.parse. This is the narrowest fix for the problem.
2016-09-22 18:06:22 -04:00
..
couchdbeditor.html Using brace to load Ace. Ace and jsonlint are now packed by default with JSONEditor. Removed all redundant build stuff for the assets. 2015-02-27 21:54:04 +01:00
largefile.json first commit 2012-04-21 13:28:28 +02:00
test_bootstrap.html Updated history and bootstrap test file 2016-04-11 21:42:38 +02:00
test_build.html Fixed #259: when having a JSONEditor inside an HTML form, clicking an entry in the context menu did submit the form 2016-01-19 21:52:52 +01:00
test_build_min.html Implemented method `setSchema` 2016-01-12 13:16:13 +01:00
test_destroy.html Added some test pages 2016-03-20 15:56:28 +01:00
test_materialize.html Fixed #289: Some CSS breaking when using the editor in combination with materialize.css or bootstrap 2016-04-09 20:55:07 +02:00
test_minimalist_min.html Added build script for minimalist version 2016-01-12 11:38:38 +01:00
test_schema.html Fixed an issue with a horiziontal scrollbar popping with a popover on displayed on the right side 2016-01-14 20:04:45 +01:00
util.test.js Fix https://github.com/josdejong/jsoneditor/issues/314 2016-09-22 18:06:22 -04:00