v8.0.3

8.0.3 (2019-09-24)

Bug Fixes

• Upgrade package dependencies and adapt sources (9f1f332)

v8.0.2

8.0.2 (2019-07-04)

Bug Fixes

• Put only the reason of the error to the error.reason property when the custom parser is used; not the full message including the error context (8d7f0b1)

v8.0.1

8.0.1 (2019-07-04)

Bug Fixes

• Update newline replacement regex to show correct error position on Windows (7af364c)

v8.0.0

8.0.0 (2019-06-16)

Bug Fixes

• Give the schema-drafts.js proper name and path in source maps (c2f0148)

Features

• Add the tokenize method returning tokens instead of the parsed object (cc7b554)
• Improve schema error reporting to the level of data parsing (ea5a8a2)
• Remove deprecated exports Parser and parser (8bda5b1)

BREAKING CHANGES

• The Parser class and parser instance did not bring any benefit. They were generated by Jison. After abandoning the Jison parser they were kept for compatibility only. The only method on the Parser prototype was the parse. It remains unchanged as a direct export. Drop the class interface and just call the parse method directly.

v7.0.3

7.0.3 (2019-06-03)

Bug Fixes

• Ensure, that tokens and keys in error messages are enclosed in quotation marks (2149198)

v7.0.2

7.0.2 (2019-06-02)

Bug Fixes

• Upgrade minificating module (04d80d7)

v7.0.1

7.0.1 (2019-06-02)

Bug Fixes

• Recognize boxed string as schema environment too (e37b004)

v7.0.0

7.0.0 (2019-06-02)

Bug Fixes

• Do not use the native parser in Safari and Node.js 4 (a4a606c)
• Include the minified scripts used on the on-line page in the NPM module (03561ec)

Features

• Add "mode" parameter to set flags for a typical formt type easier (9aa09fb)
• Add an option for ignoring trailing commas in object and arrays (7d521fb)
• Add an option for reporting duplicate object keys as an error (09e3977)
• Replace the parser generated by Jison with a hand-built parser from JJU (2781670)
• Support reviver from the native JSON.parse method (83cd33c)

BREAKING CHANGES

• There is no yy.parseError to intercept error handling. Use the thrown error - it contains all available information. The error does not include the hash object with structured information. Look for the documented properties. The location of the error occurrence is available as location.start, for example. This error reporting was enabled earlier by the limitedErrorInfo option, which is implied enabled thus ignored now.

DEPRECATION: The only exposed object to use from now on is the parse method as a named export. Other exports (parser and Parser) are deprecated and will be removed in future.

The parser from "Utilities to work with JSON/JSON5 documents" is four times faster, than the prevous one, has approximatly the same size and can be easier enhanced, regarding both features and error handling.

v6.3.1

6.3.1 (2019-05-31)

Bug Fixes

• Recognise the location of error occurrences in Firefox (7c8c040)

v6.3.0

6.3.0 (2019-05-30)

Bug Fixes

• Auto-detect the version of the JSON Schema draft by default (1fe98ef)
• Prefer the native JSON parser, if possible, to improve performance (1639356)

Features

• Support parser options for customisation and performance in JSON schema parsing too (d562826)