New Operation: pin add direct

Open
#12 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
testing-qa

Research direction

Start by locating how this repository records command operations, then run the listed add, refs, unpin, and direct-pin commands with a file larger than 256k. Done when pin list marks the hash as direct rather than recursive and, after garbage collection, child hashes are inaccessible as described in the GC note.

Written by the indexing model from the issue text.

Description

enhancement

Commands

  • add a file (greater than 256k)
  • run a refs -r to get all hashes
  • unpin it
  • add a direct pin (ipfs pin add -r=false)

Validation

  • hash shows up in pin list as a direct pin, and not as a recursive one
  • after a GC, child hashes are no longer accessible (see GC note)
Dominant language
JavaScript
Stars
2
Forks
0
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dignifiedquire/randor

All issues in dignifiedquire/randor

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.