OpenZeppelin / OpenZeppelin/contracts-wizard
Use package entry points for core
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 294
- Forks
- 186
- Avg merge
- 6h 46m
- Merged PRs (30d)
- 22
Description
See https://github.com/OpenZeppelin/contracts-wizard/pull/271#discussion_r1261826625
Use package entry points for zip-hardhat, zip-foundry, and anything that is needed for the Wizard API.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the discussion on pull request 271 and the packages/core README to identify the package entry points required by zip-hardhat, zip-foundry, and the Wizard API. Done means these consumers use the intended package entry points rather than internal paths, with all required entry points covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100