OpenZeppelin / OpenZeppelin/compact-contracts
Repo Structure Discussion: Consider defining one package for `token` and have all the token modules live there
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 55
- Forks
- 29
- Avg merge
- 5d 7h
- Merged PRs (30d)
- 25
Description
A possible future todo/discussion: consider defining one package for token and have all the token modules live there
Originally posted by @andrew-fleming in https://github.com/OpenZeppelin/midnight-contracts/pull/19#discussion_r2150559483
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
Review the current package layout and the token modules, then read the linked pull request discussion for the original context. Define the intended package organization and confirm the project agrees on the scope before treating the restructuring as done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100