Document viem support for Hardhat Upgrades#188
Draft
ericglau wants to merge 13 commits into
Draft
Conversation
✅ Deploy Preview for openzeppelin-docs-v2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documentation Pull Request
Summary
Updates the Hardhat Upgrades docs to cover using the plugin with viem, alongside the existing ethers usage.
@openzeppelin/hardhat-upgrades/viem, contracts by name, viem contract instances) and a short note on how it differs from ethers.Emphasizes throughout that viem users must import from
@openzeppelin/hardhat-upgrades/viem, since the examples otherwise use ethers.Type of Change
Related Issues
OpenZeppelin/openzeppelin-upgrades#1279
Checklist
pnpm run buildpnpm run check