We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
rpc
as described in #2004
alloy/crates/rpc-types-engine/src/payload.rs
Lines 827 to 832 in 0fbc37d
right now if we have a ExecutionPayloadV3 json, we can still do: let payload: ExecutionPayloadV2 = serde_json::from_str(json).unwrap(); and extra fields just implicitly get ignored. but obv you can no longer roundtrip then.
right now if we have a ExecutionPayloadV3 json, we can still do: let payload: ExecutionPayloadV2 = serde_json::from_str(json).unwrap();
ExecutionPayloadV3
let payload: ExecutionPayloadV2 = serde_json::from_str(json).unwrap();
and extra fields just implicitly get ignored. but obv you can no longer roundtrip then.
Originally posted by @siosw in #2004
a custom deserde impl could enforce that executionpayload can only be deserialized into the correct version
@mattsse i think i have a PR that fixes this but it adds a lot of boilerplate, maybe there is a better way to do it
The text was updated successfully, but these errors were encountered:
closed by #2017
Sorry, something went wrong.
No branches or pull requests
Component
rpc
Describe the feature you would like
as described in #2004
alloy/crates/rpc-types-engine/src/payload.rs
Lines 827 to 832 in 0fbc37d
Originally posted by @siosw in #2004
a custom deserde impl could enforce that executionpayload can only be deserialized into the correct version
Additional context
@mattsse i think i have a PR that fixes this but it adds a lot of boilerplate, maybe there is a better way to do it
The text was updated successfully, but these errors were encountered: