-
Notifications
You must be signed in to change notification settings - Fork 48
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
[Feature] Impl OpExecutionData
behaviour
#421
Labels
A-rpc-types-engine
Area: rpc-types-engine crate
Comments
@emhane we would also need |
I can take this one |
github-merge-queue bot
pushed a commit
that referenced
this issue
Feb 13, 2025
<!-- Thank you for your Pull Request. Please provide a description above and review the requirements below. Bug fixes and new features should include tests. Contributors guide: https://github.com/alloy-rs/core/blob/main/CONTRIBUTING.md The contributors guide includes instructions for running rustfmt and building the documentation. --> <!-- ** Please select "Allow edits from maintainers" in the PR Options ** --> ## Motivation Ref #421 <!-- Explain the context and why you're making that change. What is the problem you're trying to solve? In some cases there is not a problem and this can be thought of as being the motivation for your change. --> ## Solution Implemented some functions for `OpExecutionData` similar to `ExecutionData` from alloy <!-- Summarize the solution and provide any necessary context needed to understand the code change. --> ## PR Checklist - [ ] Added Tests - [x] Added Documentation - [ ] Breaking changes --------- Co-authored-by: Emilia Hane <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Component
rpc-types-engine
Describe the feature you would like
Impl
OpExecutionData
behaviour. Refer to behaviour of alloy typeExecutionData
.Additional context
blocked by #417
The text was updated successfully, but these errors were encountered: