Update the config reference related to forking.blockNumber#254
Update the config reference related to forking.blockNumber#254alcuadrado merged 1 commit intomainfrom
forking.blockNumber#254Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Pull request overview
Updates the configuration reference documentation to reflect that forking.blockNumber can be provided as a bigint.
Changes:
- Document
networks.*.forking.blockNumberas acceptingnumber | bigintinstead of onlynumber.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - `forking`: An object that describes the forking configuration and can have the following fields: | ||
| - `url`: a URL that points to a JSON-RPC node with state that you want to fork off. There's no default value for this field. It must be provided for the fork to work. | ||
| - `blockNumber`: an optional number to pin which block to fork from. If no value is provided, the latest block is used. | ||
| - `blockNumber`: an optional number or bigint to pin which block to fork from. If no value is provided, the latest block is used. | ||
| - `enabled`: an optional boolean to switch on or off the fork functionality. Default value: `true` if `url` is set, `false` otherwise. |
There was a problem hiding this comment.
This update documents networks.*.forking.blockNumber as number | bigint, but the same option is described later under “Solidity tests configuration” (test.solidity.forking.blockNumber) as just an “Optional block number” (no mention of bigint). Given the forking guide includes a bigint example (blockNumber: 23819000n), it’d be good to update that later reference too for consistency and to avoid confusing users.
No description provided.