Added support for unquoted String Values #1
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.
I've found lately JSONs with unquoted String values (it seems to be called relaxed json), so I've updated the code to support those:
In this version, if you set the setting
JsonOptions.AllowUnquotedKeys
toTrue
it will also allow unquoted Strings. Unquoted Strings (in this version) end once we find a space, a coma, a "}" or a "]".Notice that this will capture the true/false/null/numbers as strings (not having the quotes to identify the strings, all are a potential Strings), so we check them afterwards and:
IsNumeric()
we convert the value back to number usingVBA.Val()
.Null
True
/False
Next steps: We should clarify the setting
JsonOptions.AllowUnquotedKeys
: (a) rename it to clarify it works for both key and values or (b) create a new setting to allow unquote key/values separately.