BREAKING(jsonc): remove allowTrailingComma
option
#5119
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What's changed
This change removes the
ParseOptions.allowTrailingComma
option, and therefore theParseOptions
interface. For now on, trailing commas are allowed (the previous default) without the ability to change.Why this change was made
This change was made because setting
ParseOptions.allowTrailingComma
tofalse
seemed to lack any useful use case. Also, having this added control also added some logic overhead. By removing this option, we slightly simplify the API surface of@std/jsonc
while still remaining compatible with the majority of existing use cases.Migration guide
No further action is needed for users that didn't use the
options
argument ofparse()
or setoptions.allowTrailingComma
totrue
.For users that set
options.allowTrailingComma
tofalse
,parse()
now no longer throws aSyntaxError
when it encounters a trailing comma.