fix: improve CallTracer type detection for transaction tracing #2010
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
User description
Enhance the default trace generation for CallTracer by dynamically determining the transaction type (CALL or CREATE) based on the presence of a 'to' address
PR Type
Enhancement, Bug fix
Description
Improve CallTracer type detection for transaction tracing
Dynamically determine transaction type (CALL or CREATE)
Base type on presence of 'to' address
Enhance default trace generation for CallTracer
Changes walkthrough 📝
evm.rs
Implement dynamic transaction type detection in CallTracer
src/eth/executor/evm.rs
default_trace
function for CallTracer.into()
conversion