neume-network / neume-network/data
Integrate missing call-tokenuri platforms into crawlpath at steps/3.mjs
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 15
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
- By using the generic call-tokenuri function, we've been deleting the platform-specific call-tokenuri strategies: https://github.com/neume-network/strategies/commit/08af9f4fecdedad92cf5e8b5c6558f0189b97c12
- But they're still available here as permalinks in git
- And once we integrate those platforms into /data, we can use the filter and signature functions here
- https://github.com/neume-network/strategies/blob/57e4f2cf92f28307e7ed6d6a2c9d7ab810c82bf4/src/strategies/sound-protocol-call-tokenuri/extractor.mjs
- https://github.com/neume-network/strategies/blob/57e4f2cf92f28307e7ed6d6a2c9d7ab810c82bf4/src/strategies/zora-drops-call-tokenuri/extractor.mjs
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 in steps/3.mjs and compare the referenced sound-protocol-call-tokenuri and zora-drops-call-tokenuri extractor.mjs files. Trace how platforms are integrated into /data, then use the available filter and signature functions for the missing platforms. Done means those platforms are represented in crawlpath at the indicated step.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- blockchain, data
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100