MetaMask / MetaMask/create-release-branch
Integrate `package-manifest` with `@metamask/action-utils`
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 9
- Forks
- 7
- Avg merge
- 51m
- Merged PRs (30d)
- 2
Description
When adding code that reads/parses the manifest for a package, I decided not to use the types and functions exported by package-utils from @metamask/action-utils, but write my own instead. I wanted a type that represented an unvalidated manifest and a type that represented a validated manifest, and I didn't feel like I needed separate types for a monorepo package vs. polyrepo package. Once we work these types out then we should work out how we can integrate them with action-utils so that other projects can use them.
Contributor guide
No contributing guide indexed for this repository
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 by locating the package-manifest implementation and the package-utils types and functions exported by @metamask/action-utils. Compare the unvalidated and validated manifest representations, then establish the shared types and integration needed for other projects to consume them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100