Adding support for an extra json_encode argument for empty table encoding resolution #48
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.
The extra argument should be a table which, when looked up with an empty table key, would yield a truthy value if that empty table should be encoded as a JSON empty array (
[]
) instead of an empty object ({}
).Needless to say, the lookup table's metatable is honored so you can in fact do pretty much any checks in its
__index
metamethod.This is more flexible than #15 and doesn't require modifying the encoded data like #25.