jsonc-parser

Changes:

• #92: remove exports, prepare 3.3.1

This list of changes was auto generated.

Changes:

Feature Requests:

• #11: Can we have a "insertFinalNewline" option in "FormattingOptions"?
• #4: Source map referenced but not included in published package

Bugs:

• #33: Formatting valid json content is causing an invalid json
• #40: parseTree() returns undefined on empty string input

Others:

• #90: prepare 3.3.0
• #88: Allow the visitor to cease callbacks
• #89: Bump braces from 3.0.2 to 3.0.3

• #84: prepare 3.2.1
• #81: perf(format): cache breaklines and spaces as much as possible
• #79: update dependencies
• #75: ci: add batch
• #72: delete pr-chat action
• #71: add publish pipeline & cleanup ci
• #70: set preserveConstEnums: true, switch to es2020
• #69: sort edits in applyEdits
• #66: An additional parameter keepLines has been added into the formatting options which allows to keep the original line formatting
• #64: Adding Microsoft SECURITY.MD
• #62: Add JSON path supplier parameter to visitor functions
• #44: findNodeAtLocation does not handle incomplete property pair
• #61: Update API section in README
• #53: Clarify whether / how Edit[] can be concatenated
• #46: Non-standard whitespace handling
• #47: Improve README
• #54: readme: improve ParseOptions documentation
• #43: Add file extenstion to typings property value
• #34: Optimize parseLiteral for number-heavy JSON files (ala GeoJSON)
• #39: Bump lodash from 4.17.15 to 4.17.19
• #35: Allow for array modifications, add inPlace formatting option.
• #32: Parse errors make parsed tree useless
• #31: Upgrading from 2.1.1 to 2.2.0 has diagnostic for file with only comments
• #25: Fix typo in README
• #24: parse function should include properties with empty string as their keys
• #21: Update README.md
• #18: JavaScipt -> JavaScript
• #17: add line and column information to scanner and visitor
• #15: Fix a few typos in doc comments
• #12: Do not mutate the given path
• #9: Refactor computeIndentLevel method
• #8: Fix typo of token
• #6: Allow trailing commas in array
• #5: add JSON formatter and editor from VS Code
• #1: Error objects should also contain location information

This list of changes was auto generated.

prepare 3.2.1 (#84)

set preserveConstEnums: true, switch to es2020 (#70)

An additional parameter keepLines has been added into the formatting …

• fixed API spec for parseTree. Can return undefine for empty input.
  • added new API FormattingOptions.insertFinalNewline.

• new API ModificationOptions.isArrayInsertion: If JSONPath refers to an index of an array and isArrayInsertion is true, then modify will insert a new item at that location instead of overwriting its contents.
  • ModificationOptions.formattingOptions is now optional. If not set, newly inserted content will not be formatted.

• added ParseOptions.allowEmptyContent. Default is false.
  • new API getNodeType: Returns the type of a value returned by parse.
  • parse: Fix issue with empty property name

• JSONScanner and JSONVisitor return lineNumber / character.

• renamed Node.columnOffset to Node.colonOffset
  • new API getNodePath: Gets the JSON path of the given JSON DOM node
  • new API findNodeAtOffset: Finds the most inner node at the given offset. If includeRightBound is set, also finds nodes that end at the given offset.

• provide ems modules

• added the visit.onComment API, reported when comments are allowed.
  • added the ParseErrorCode.InvalidCommentToken enum value, reported when comments are disallowed.

• added the format API: computes edits to format a JSON document.
  • added the modify API: computes edits to insert, remove or replace a property or value in a JSON document.
  • added the allyEdits API: applies edits to a document

• remove nls dependency (remove getParseErrorMessage)