ReMarkable NFTs V2
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
This issue is a brain dump what needs to be done to successfully finish RMRK v2 in minimark package.
### PLEASE BE AWARE THERE IS PR #43 FOR THAT
Critital
- [ ] Test Resources logic against the `rmrk-tools` package (inspo is written for create)
- [ ] Comply resource spec with `rmrk-tools` (we have different types than the package)
- [ ] Comply EQUIP - (Equip a child NFT into a parent's slot, or unequip)
- [ ] Comply EQUIPPABLE
- [ ] Comply SETPROPERTY
- [ ] Comply SETPRIORITY
- [ ] Comply THEMEADD
**⚠️ For all critical stuff, unit test against `rmrk-tool` need to be written ⚠️**
Minor
- [ ] `createBase` should take multiple parameters instead of object
Miscelanous
- [ ] fix the issue that is creating multiple `minimarks` in build
Contributor guide
No contributing guide indexed for this repository
Research direction
Start in the minimark package and review the existing RMRK v2 implementation, especially resource handling, EQUIP, EQUIPPABLE, SETPROPERTY, SETPRIORITY, THEMEADD, createBase, and the build path. Compare behavior with the rmrk-tools package and inspect PR #43 for prior work. Done means the listed compatibility work and unit tests are complete, createBase has the requested interface, and the build no longer creates multiple minimarks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100