Skip to content
This repository was archived by the owner on Feb 12, 2024. It is now read-only.

refactor: return promise from dag resolve #3152

Merged
merged 9 commits into from
Jul 9, 2020

Conversation

achingbrain
Copy link
Member

@achingbrain achingbrain commented Jul 8, 2020

Makes ipfs.dag.resolve behave the same when calling into core and over the http api.

Adds documentation and interface tests for ipfs.dag.resolve.

Supersedes #3131
Fixes #2962

BREAKING CHANGES:

  • ipfs.dag.resolve returns Promise<{ cid, remainderPath } instead of AsyncIterator<{ value, remainderPath }>
    • Previously the core api returned an async iterator and the http client returned a simple promise

@achingbrain achingbrain merged commit f20cdf1 into master Jul 9, 2020
@achingbrain achingbrain deleted the refactor/return-promise-from-dag-resolve branch July 9, 2020 10:48
SgtPooki referenced this pull request in ipfs/js-kubo-rpc-client Aug 18, 2022
Makes `ipfs.dag.resolve` behave the same when calling into core and over the http api.

Adds documentation and interface tests for `ipfs.dag.resolve`.

Supersedes #3131
Fixes #2962

BREAKING CHANGES:

- `ipfs.dag.resolve` returns `Promise<{ cid, remainderPath }` instead of `AsyncIterator<{ value, remainderPath }>`
  - Previously the core api returned an async iterator and the http client returned a simple promise

Co-authored-by: Tarun Batra <[email protected]>
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.

dag.resolve has different return type in http-client
2 participants