Matt Solomon

Ah I see. Though I don't follow see the use case for it / when would you need to do that? FWIW you can also `vm.etch` any code you want...

Seems like a niche use case so I'm not sure it's worth a cheatcode, but an issue in the foundry repo would be the right place to discuss that. >...

Pushed a commit which adds a failing test, possibly related to what @ZeroEkkusu mentioned. Didn't try debugging yet, but it really does bloat the trace 😅

Probably should change them all to `camelCase` for consistency with the rest of forge-std cheat names, but doing so would be a breaking change so I think we leave the...

Are you seeing an error when compiling, or just in the VSCode tooltip? I suspect it may just be an issue with VSCode/the extension

I'd say PRs for things like this into `console2.sol` are good, but we should leave `console.sol` 1:1 with hardhat. @ZeroEkkusu let me know if that seems reasonable. > And couldn't...

Now that `vm.parseJson` is merged (thanks a lot @odyslam!) let's revisit this PR and get the required Vm interface updates, types, and any helpers merged

If I rebase locally against main all tests pass, seems this branch is missing the `projectRoot` cheatcode definition from https://github.com/foundry-rs/forge-std/pull/158, so let's try that and see if it fixes CI?...

I'd say three things left before merging this, all easy things at this point - [x] Refactor into a library using this approach: https://github.com/foundry-rs/forge-std/pull/138#discussion_r956749279 - [x] Make sure we track...

Yea I don't know why the CI is failing, I'm gonna take a closer look later today so don't worry about it