feat: add support for serializing complex objects #49
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
43081j
force-pushed
the
complex-obj
branch
4 times, most recently
from
012700f to
7bd663a
Compare
Adds a `shouldSerializeObject` function which determines if a value should be serialized or should attempt to be nested. The default implementation checks if a value is a non-date object, meaning all objects which are not dates will trigger nesting.
43081j
added a commit
that referenced
this pull request
Jul 27, 2024
feat: add support for serializing complex objects (#49)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds a
shouldSerializeObjectfunction which determines if a value should be serialized or should attempt to be nested.The default implementation checks if a value is a non-date object, meaning all objects which are not dates will trigger nesting.
Fixes #48