v3.3.0
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
undefinedon empty string input
Others:
See More
- #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.