-
Notifications
You must be signed in to change notification settings - Fork 172
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
Support non-standard fields in Response #1349
Comments
Hey hey,
Sorry about that I changed the deserialization of the responses to a manual implementation but forgot about that, fixed in #1353
What we could is to introduce another field Thus, I think it's fine to add to another field |
Thanks for replying.
Problem is RawValue is not sized. Would Also, I want to get access to the fields, and |
Yeah, you could use either |
Well, here it is: thebabush@84130ec However, that hashmap is useless atm. |
Hello,
I'm interacting with a server that sends additional fields in the response message. The fields contain data I care about, so I can't even simply patch jsonrpsee to ignore them (right now jsonerpsee just asserts due to unknown field).
I'm down to make a PR, but I'd like to know if you could guide me through the most painless way to implement this?
Seems like the easiest way would be to extend Response/Notification/etc to have some kind of
unknowns: Value
, but that would mean dynamic allocations + requiring a feature flag, which is ugly.Thanks.
The text was updated successfully, but these errors were encountered: