Skip to content

feat: add dag-json resolver #397

New issue

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

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

Already on GitHub? # to your account

Merged
merged 1 commit into from
Jan 16, 2024
Merged

Conversation

alanshaw
Copy link
Member

Basically the same as dag-cbor...allows the exporter to walkPath and export dag-json encoded data.

@achingbrain achingbrain merged commit 1b40e3e into master Jan 16, 2024
@achingbrain achingbrain deleted the feat/add-dag-json-resolver branch January 16, 2024 15:33
github-actions bot pushed a commit that referenced this pull request Jan 16, 2024
## [ipfs-unixfs-exporter-v13.3.0](ipfs-unixfs-exporter-v13.2.5...ipfs-unixfs-exporter-v13.3.0) (2024-01-16)

### Features

* add dag-json resolver ([#397](#397)) ([1b40e3e](1b40e3e))
Copy link

🎉 This PR is included in version 11.1.3 🎉

The release is available on npm package (@latest dist-tag)

Your semantic-release bot 📦🚀

Copy link

🎉 This PR is included in version 15.2.4 🎉

The release is available on npm package (@latest dist-tag)

Your semantic-release bot 📦🚀

achingbrain added a commit that referenced this pull request Feb 2, 2024
The json codec is included in the multiformats module so no extra
deps are needed.

Similar to #397
achingbrain added a commit that referenced this pull request Feb 2, 2024
The json codec is included in the multiformats module so no extra
deps are needed.

Similar to #397
achingbrain added a commit that referenced this pull request Feb 2, 2024
The json codec is included in the multiformats module so no extra
deps are needed.

Similar to #397
github-actions bot pushed a commit that referenced this pull request Feb 2, 2024
## ipfs-unixfs-exporter [13.5.0](ipfs-unixfs-exporter-13.4.0...ipfs-unixfs-exporter-13.5.0) (2024-02-02)

### Features

* add json resolver ([#400](#400)) ([81e85c8](81e85c8)), closes [#397](#397)
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants