Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use valid IPFS content paths #21

Closed
lidel opened this issue Aug 3, 2021 · 0 comments
Closed

Use valid IPFS content paths #21

lidel opened this issue Aug 3, 2021 · 0 comments
Assignees
@martinheidegger
Labels
P3 Low: Not priority right now

Comments

@lidel
Copy link
Contributor

lidel commented Aug 3, 2021 •
edited
Loading

General ask for entire test suite: do not use invalid IPFS paths. We have a policy that every CID or /ipfs/ content path published in specs, docs, repos or tests should resolve, unless we test failure scenario.

  • either use valid IPFS CIDs and paths like /ipfs/bafkqae2xmvwgg33nmuqhi3zajfiemuzahiwss or /ipfs/bafybeiaysi4s6lnjev27ln5icwm6tueaw2vdykrtjkwiphwekaywqhcjze/wiki/Ancient_Greece
  • or some fake namespaces like /foo/bar /bar/buz/zzz
@lidel lidel changed the title Cleanup content paths Use valid IPFS content paths Aug 3, 2021
@lidel lidel added the P3 Low: Not priority right now label Aug 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@martinheidegger martinheidegger

Labels
P3 Low: Not priority right now
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lidel @martinheidegger