-
Notifications
You must be signed in to change notification settings - Fork 5k
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
[plugin] customTransactionSchema follow-up #7273
Comments
I'm happy to propose changes but I just wanted to get your opinion on what you think should happen, I believe the function is somewhat redudant and could be limited to field aliasing (data<->input, gas<->gasLimit) |
This was referenced Sep 20, 2024
@nicolasbrugneaux considering getEthereumjsTxDataFromTransaction is used
|
what about a test in web3 like "allows for plugins to add new tx fields" to make sure this works and prevent regressions |
15 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Greetings! Thanks again for merging my work in
Sadly, it's still not enough to allow for extra fields in transactions. Indeed, this function
getEthereumjsTxDataFromTransaction
is trimming down fields despite being validated earlierThe text was updated successfully, but these errors were encountered: