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.

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

CoreAPI progress tracking issue #4498

Open
39 of 51 tasks
magik6k opened this issue Dec 15, 2017 · 3 comments
Open
39 of 51 tasks

CoreAPI progress tracking issue #4498

magik6k opened this issue Dec 15, 2017 · 3 comments
Labels
topic/core-api Topic core-api topic/meta Topic meta

Comments

@magik6k
Copy link
Member

magik6k commented Dec 15, 2017

This issue is for tracking progress on the CoreAPI package

blockers:

related issues:

List of APIs to support (apis with bold names what is needed to replace go-ipfs-api with coreapi-based implementation without removing features, add more if I forgot something):

(I'm aware of ipfs-inactive/interface-js-ipfs-core#66, I'd say that this interface should get to a 'mostly done' stage here as it's much easier to refine it while it's in one place)

@magik6k magik6k added the topic/meta Topic meta label Dec 15, 2017
@ghost
Copy link

ghost commented Dec 16, 2017

Thanks so much, great work :)

@magik6k magik6k changed the title CoreAPI progress tracking PR CoreAPI progress tracking issue Dec 16, 2017
@ghost ghost added the topic/core-api Topic core-api label Dec 16, 2017
@ghost
Copy link

ghost commented Dec 17, 2017

what is needed to replace go-ipfs-api with coreapi-based implementation without removing features

We can just modify the Shell functions to use the CoreAPI under the hood.

@daviddias
Copy link
Member

@magik6k ❤️ Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic/core-api Topic core-api topic/meta Topic meta
Projects
None yet
Development

No branches or pull requests

2 participants