Some people have bumped into the issue where the new forge had issues with new forge's build not being parsed. This fixes the issue. We now:
Use new forge internally
Don't parse JSON's that are new and not useful for us
Need --ast flag as per:forge build --ast. This was the default previously.
Allow Env to be pushed down into the JSON parsing part so we can debug more effectively using --debug
This needs updater to the docs, too, due to --ast. This is unfortunate, we only need it to know the absolutePath whicih is actually a relative path like `src/multiply-test.sol"
I had to move writeTraceDapp and writeTrace because of circular dependency issues. I think putting it in EVM.UnitTest is not a bad place. Feedback welcome, though.
Description
Some people have bumped into the issue where the new
forge
had issues with new forge's build not being parsed. This fixes the issue. We now:forge
internally--ast
flag as per:forge build --ast
. This was the default previously.Env
to be pushed down into the JSON parsing part so we can debug more effectively using--debug
This needs updater to the docs, too, due to
--ast
. This is unfortunate, we only need it to know theabsolutePath
whicih is actually a relative path like `src/multiply-test.sol"I had to move
writeTraceDapp
andwriteTrace
because of circular dependency issues. I think putting it inEVM.UnitTest
is not a bad place. Feedback welcome, though.Checklist