CID related logic should not live in dmap.js
Open
- Dominant language
- JavaScript
- Stars
- 59
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Interpreting meta/data as a CID is an application level thing
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading dmap.js and tracing how meta/data are interpreted as CIDs. Identify the application boundary that should own this interpretation; done means CID-related logic no longer lives in dmap.js while the intended behavior remains clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100