Skip to content
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

Closed
nicolasbrugneaux opened this issue Sep 20, 2024 · 4 comments · Fixed by #7282
Closed

[plugin] customTransactionSchema follow-up #7273

nicolasbrugneaux opened this issue Sep 20, 2024 · 4 comments · Fixed by #7282

Comments

@nicolasbrugneaux
Copy link
Contributor

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 earlier

@nicolasbrugneaux
Copy link
Contributor Author

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)

@jdevcs
Copy link
Contributor

jdevcs commented Sep 23, 2024

@nicolasbrugneaux considering getEthereumjsTxDataFromTransaction is used

getEthereumjsTxDataFromTransaction(formattedTransaction),
I think it can be modified to use alias for (data<->input, gas<->gasLimit) and spread all existing other fields from the transaction to return obj.

@aaronmgdr
Copy link

what about a test in web3 like "allows for plugins to add new tx fields" to make sure this works and prevent regressions

@nicolasbrugneaux
Copy link
Contributor Author

nicolasbrugneaux commented Sep 23, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants