-
Notifications
You must be signed in to change notification settings - Fork 112
-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal: support for embedded / raw json #18
Comments
Hi, thank you for your proposal, as discussed before, it is definitely an interesting feature. I'm going to review your implementation and will let you know my feedback as soon as possible. |
Great,
maj-o is my private nick.
Regards
Andreas
LG Andreas
…-----Original Message-----
From: Francois Parquet <notifications@github.com>
To: francoispqt/gojay <gojay@noreply.github.com>
Cc: Andreas <ajmatuschek@gmail.com>, Author <author@noreply.github.com>
Sent: Sa., 05 Mai 2018 18:10
Subject: Re: [francoispqt/gojay] Proposal: support for embedded / raw json (#18)
Hi, thank you for your proposal, has discussed before, it is definitely an interesting feature.
I'm going to review your implementation and will let you know my feedback as soon as possible.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#18 (comment)
|
Hi Andreas, Sorry was a bit late yesterday when I started reviewing your proposal (I live in Hong Kong). I am creating a branch, where I will add the feature. branch name: If you want to contribute you can submit pull request to that branch. When ready will merge the branch along with another branch where I added some optimisations, this will be a new release 0.10.5. |
Pull request is open here #19 |
I renamed Also on the decoding part, I am returning an error if the EmbeddedJSON is a nil pointer. |
Version 0.10.5 has been released. Will add documentation when I have time. Closing the issue. |
C H A P E A U ! Had no time to take a look earlier. |
Some kind of embedded json saved handled as raw []byte is usefull.
If the type of value does not matter or is unknown at this point of computation. Taking a modified json rpc request as example for test, shows the benefits. A router is interested in id and method. The method itself is interested in params. So params should not be routers problem. I made the changes, so it works for me. It would be great, if the code could be reviewed and added in some way.
Proposed code for decoder.go:
QUICK TEST:
I know test is not complete - but shows, what the benefits are.
For json rpc the params are important inside of the method using them.
This change would make things simpler (simpler ist better ;-)
ENCODER:
Encoder, Decoder Test:
The text was updated successfully, but these errors were encountered: