jsonc-parser

Changes

Feature Requests

• Can we have a "insertFinalNewline" option in "FormattingOptions"?

• Source map referenced but not included in published package

Bugs

• Formatting valid json content is causing an invalid json

• parseTree() returns undefined on empty string input

Others

• Prepare 3.3.0

• Allow the visitor to cease callbacks

See More

• Prepare 3.2.1

• format: Cache breaklines and spaces as much as possible

• Delete pr-chat action

• Add publish pipeline & cleanup ci

• Set preserveConstEnums: true, switch to es2020

• Sort edits in applyEdits

• An additional parameter keepLines has been added into the formatting options which allows to keep the original line formatting

• Adding Microsoft SECURITY.MD

• Add JSON path supplier parameter to visitor functions

• findNodeAtLocation does not handle incomplete property pair

• Update API section in README

• Clarify whether / how Edit can be concatenated

• Non-standard whitespace handling

• Improve README

• readme: Improve ParseOptions documentation

• Add file extenstion to typings property value

• Optimize parseLiteral for number-heavy JSON files (ala GeoJSON)

• Allow for array modifications, add inPlace formatting option.

• Parse errors make parsed tree useless

• Upgrading from 2.1.1 to 2.2.0 has diagnostic for file with only comments

• Parse function should include properties with empty string as their keys

• Update README.md

• JavaScipt -> JavaScript

• Add line and column information to scanner and visitor

• Do not mutate the given path

• Refactor computeIndentLevel method

• Allow trailing commas in array

• Add JSON formatter and editor from VS Code

• Error objects should also contain location information

This list of changes was auto generated.