zerosnacks comments

Results 379 comments of


                                            zerosnacks

feat(`compatibility`): use EIP-55 checksummed address notation in Anvil and Forge outputs

> @zerosnacks could i take this one? Sure! Assigning to you

feat(`compatibility`): use EIP-55 checksummed address notation in Anvil and Forge outputs

> users actually expect a lowercase format and implementing variation of the format should be on the consumer/ui side, so to be decided if we should actually implement this or...

bug(`cheatcodes`): `vm.parseJsonUint` can't parse numbers with scientific notation

Hi @francesco-gaglione, thanks for narrowing this down. I think the correct place to implement this would be `alloy/core`.

feat(anvil): Set anvil fork cache location (`--cache-path`)

Marking as duplicate of https://github.com/foundry-rs/foundry/issues/3512 which aims to add an Anvil cache path

feat: `forge dependencies` to list details about installed dependencies

Hey @mario-eth, would this be something you are interested in working on? Scope would be to display both `.gitmodules` dependencies like this and the `soldeer` dependencies in a unified view

feat: `forge dependencies` to list details about installed dependencies

Awesome! Thanks

feat: `forge dependencies` to list details about installed dependencies

Related: in https://github.com/foundry-rs/foundry/pull/9522 we are introducing a `foundry.lock` file that will be able to be easily inspected as it is plain pretty formatted JSON.

Optimism Hardfork Support

Thanks @ewoolsey! Approach looks good to me, pending reviews of others

bug(`forge test`): JSON output should consistently adhere to verbosity flags

Hi @bowd, regarding (1): I think `--json` should consistently adhere to verbosity rules. If you could point to cases where this is not the case this would be valuable. For...

bug(`forge test`): JSON output should consistently adhere to verbosity flags

Related: https://github.com/foundry-rs/foundry/issues/8789#issuecomment-2325892337