Ramain traces in json ouput

[suxnju]

Component

Forge

Describe the feature you would like

Ramain traces in json ouput for the latest version 0.2.0 (1bb2d67 2024-02-19T00:17:15.443050638Z) like in old version (e.g., 0.2.0 (638bd2e 2023-05-23T09:59:16.241585900Z).

version: forge 0.2.0 (1bb2d67 2024-02-19T00:17:15.443050638Z)
system: ubuntu
command: forge test --contracts ./test.sol -vvvvv -j --ffi > ./test.json
output:

{
    "test-FFI-diff.sol:DiffFuzzTest": {
        "duration": {
            "secs": 0,
            "nanos": 2566898
        },
        "test_results": {
            "test_diff()": {
                "status": "Success",
                "reason": null,
                "counterexample": null,
                "logs": [],
                "decoded_logs": [],
                "kind": {
                    "Standard": 207879
                },
                "labeled_addresses": {},
                "debug": null,
                "breakpoints": {}
            }
        },
        "warnings": []
    }
}

expected behavior: traces in test_diff()

Additional context

I have a small question, the result display in console and export the json are different, how to achieve consistency?

For example, the returned data of VM::stopAndReturnStateDiff() is structed like

But the data in json file is raw data. Here, I used old version 0.2.0 (638bd2e 2023-05-23T09:59:16.241585900Z)`.

[onbjerg]

The JSON output is the raw ABI encoded representation of the return data.

[suxnju]

The JSON output is the raw ABI encoded representation of the return data.

Thanks for the reply, do you mean that I can only process the generated raw data in the JSON output? Can I directly utilize the functionality that Foundry has already implemented to make it processed the same as the console?

[DaniPopes]

@onbjerg I think he means that traces is missing, because it's marked with #[serde(skip)] since last refactor

[onbjerg]

Then it's a duplicate of #6922