You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By giving alias to frequently interacted contracts in foundry.toml, say [labels], could facilitate development even more. Imagine this feature as a combination of two existing feature. The first is giving alias to rpc_endpoints by [rpc_endpoint] field in foundry.toml; the second is giving alias to addresses by vm.label in scripts and tests.
Being able to use the label in cast commands, say cast send -r eth MAINNET_CONTRACT_I_CARE ..., could already save some time copy and pasting. It also helps the readability.
A further step could be extending the configured labels to all the tests and scripts as if it's in function setup(), saving the time of repeatedly using of vm.label
Additional context
No response
The text was updated successfully, but these errors were encountered:
zerosnacks
changed the title
feat(config): enable configuration of address alias in foundry.toml
feat(config): add labels field to foundry.tomlSep 11, 2024
Component
Other (please describe)
Describe the feature you would like
By giving alias to frequently interacted contracts in
foundry.toml
, say [labels], could facilitate development even more. Imagine this feature as a combination of two existing feature. The first is giving alias to rpc_endpoints by[rpc_endpoint]
field infoundry.toml
; the second is giving alias to addresses byvm.label
in scripts and tests.Being able to use the label in cast commands, say
cast send -r eth MAINNET_CONTRACT_I_CARE ...
, could already save some time copy and pasting. It also helps the readability.A further step could be extending the configured labels to all the tests and scripts as if it's in
function setup()
, saving the time of repeatedly using ofvm.label
Additional context
No response
The text was updated successfully, but these errors were encountered: