zerosnacks
zerosnacks
### Component primitives ### Describe the feature you would like From https://github.com/foundry-rs/foundry/issues/9499 by `pmerkleplant` > The ECDSA signatures generated by the `vm.sign()` cheatcode do not strictly follow RFC-6979. For more...
To simplify development we should simply move the contents of the `vocs` directory now in the root directory
See: https://github.com/foundry-rs/book/actions/runs/15369028057/job/43245643874#step:5:30 due to https://github.com/foundry-rs/book/blob/cac0984a2d564ae660c31ae1fc0aacff4f92efc9/scripts/gen_output/help.sh#L18 @yash-atreya what is the current status of the automated CLI reference documentation?
Given the book targets latest nightly most users, who are now pinned on `stable`, can run into mismatching documentation Adding an icon or emoji of some kind to indicate a...
Rather than manually maintaining the references we should fuse the CLI output that is guaranteed to be up to date with template content we insert into a unified page
This is currently missing from the book Should document inline configuration / foundry toml configuration Should cover what it does, when to use it (and when not for performance reasons)
We currently manually maintain the sections in https://book.getfoundry.sh/reference/forge-std/, I would like this to be replaced with an automated process that ideally uses purely NatSpec and file name grouping. This makes...
### Component Forge, Cast, Anvil, Chisel ### Describe the feature you would like At multiple occasions we've seen requests to make Foundry's binaries all adhere to the `foundry.toml` configuration (effectively...
### Component Forge ### Describe the feature you would like Currently a syntax like `// forge-config: default.lint.exclude_lints = ["mixed-case-variable"]` defined on a function level would correctly ignore the lint rule...
### Component Forge ### Have you ensured that all of these are up to date? - [x] Foundry - [ ] Foundryup ### What version of Foundry are you on?...