Add Support For Custom JSON Encoders/Decoders #338
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
|
We really need to support passing datetimes over the wire. Custom objects would b an added benefit. Can this be merged soon? |
samuelhwilliams
force-pushed
the
custom-json-encoder-decoder
branch
from
da32489
to
a82719f
Compare
|
Any progress on this? It would be very helpful |
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.
Updated version of #256
@samuelhwilliams I took a crack at supporting custom json encoders/decoders with this PR. It get's the job done for me and makes the new options much more general then the original.
Let me know what you think and whether or not it's missing anything or needs clarification anywhere!