create interface for integrating third-party json parsers #45
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
added 6 commits
December 3, 2020 18:57
|
@novabyte ready for another look |
* DateTime type and Guid type conversions added to TinyJson. Also tests are modified. * DateTime format changed. Because of take all the values of the DateTime * TestObjectWithAllTypes added. All known types tested from object-json to json-object
|
|
|
|
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.
The only complicated thing here is that some parsers (e.g., RapidJson) require member annotations. For any users requiring custom member annotations, the consideration would be whether to add some sort of "member annotation" hook to plug into when doing the codegen. Aside from that, this interface should do the trick.