feat(forge/script): decode execution traces when --json
is enabled
#10109
+22
−4
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.
Motivation
This PR resolves #10019.
More precisely, it ensures that the execution traces are decoded when the
--json
flag is enabled for theforge script
command.With those changes, the command prints all the decoded values and not just
null
.Solution
I forced the decoding of the traces after the execution has completed, right before the result object is encoded in JSON and printing to the stdout.
Note: I updated the existing CLI test.
PR Checklist