Skip to content
This repository has been archived by the owner on Aug 11, 2021. It is now read-only.

Adapted to new ipfs-repo API #84

Merged
merged 2 commits into from
Jul 4, 2017
Merged

Adapted to new ipfs-repo API #84

merged 2 commits into from
Jul 4, 2017

Conversation

pgte
Copy link
Contributor

@pgte pgte commented Jun 29, 2017

Still needs new relesease of ipfs-repo and ipfs-block-service.

@RichardLitt RichardLitt added the status/in-progress In progress label Jun 29, 2017
@pgte
Copy link
Contributor Author

pgte commented Jun 30, 2017

Depends on ipfs/js-ipfs-repo#140

@daviddias daviddias changed the title WIP: adapted to new ipfs-repo API Adapted to new ipfs-repo API Jul 4, 2017
src/index.js Outdated
datastore: {
db: Memdown
}
},
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pgte is this correct?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@diasdavid looks like it. I think that, for the tests, it doesn't make a difference whether we use an extension or sharing. Wouldn't you agree?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

and that, generally, without persistence, these options would be enough..

@daviddias daviddias merged commit 61915ad into master Jul 4, 2017
@daviddias daviddias deleted the feat/repo-new-api branch July 4, 2017 19:25
@daviddias daviddias removed the status/in-progress In progress label Jul 4, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants