-
Notifications
You must be signed in to change notification settings - Fork 289
refactor(iroh)!: Move blobs and tags rpc client and server to iroh-blobs #2874
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
Conversation
Documentation for this PR has been generated and is available at: https://n0-computer.github.io/iroh/pr/2874/docs/iroh/ Last updated: 2024-11-06T16:15:38Z |
d596522
to
6e66ef4
Compare
@@ -28,8 +29,7 @@ use iroh::{ | |||
}, | |||
client::{ | |||
blobs::{ | |||
BlobInfo, BlobStatus, CollectionInfo, DownloadMode, DownloadOptions, | |||
IncompleteBlobInfo, WrapOption, | |||
BlobInfo, BlobStatus, CollectionInfo, DownloadOptions, IncompleteBlobInfo, WrapOption, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will probably go away if docs are removed as well.
what about removing the fs utils you added to |
I think some of them are also used from docs, so I can't remove them all until docs are also gone... But will check. |
# Conflicts: # Cargo.lock # iroh-cli/Cargo.toml # iroh-dns-server/src/http/rate_limiting.rs # iroh/Cargo.toml
d96c6c2
to
914452c
Compare
Removed several, including stuff that needs walkdir. But there is still something left that is needed from docs. |
…obs (#2874) ## Description Move blobs and tags rpc client and server to iroh-blobs. Depends on n0-computer/iroh-blobs#7 Todo: - [x] merge n0-computer/iroh-blobs#7 ## Breaking Changes - Lots of types in client::blobs and client::tags become reexports - blob share goes away, since it requires the node client ## Notes & open questions I want to keep the client::blobs and client::tags modules self-contained, so the idea is that these will reexport all the things from iroh-blobs::rpc::client that a user will need (except I have probably forgotten something). Maybe I should use wildcard exports here even though people dislike them... ? ~~The client::blobs::Client itself is *not* a reexport but a newtype to hide the ugly type parameters. Same for client::tags::Client.~~ With the changes in quic-rpc, these are now just module reexports! The Blobs protocol handler now takes an Endpoint, since that was needed to implement one of the functions. <!-- Any notes, remarks or open questions you have to make about the PR. --> ## Change checklist - [x] Self-review. - [x] Documentation updates following the [style guide](https://rust-lang.github.io/rfcs/1574-more-api-documentation-conventions.html#appendix-a-full-conventions-text), if relevant. - [x] Tests if relevant. - [x] All breaking changes documented.
Description
Move blobs and tags rpc client and server to iroh-blobs.
Depends on n0-computer/iroh-blobs#7
Todo:
Breaking Changes
Notes & open questions
I want to keep the client::blobs and client::tags modules self-contained, so the idea is that these will reexport all the things from iroh-blobs::rpc::client that a user will need (except I have probably forgotten something). Maybe I should use wildcard exports here even though people dislike them... ?
The client::blobs::Client itself is not a reexport but a newtype to hide the ugly type parameters. Same for client::tags::Client.With the changes in quic-rpc, these are now just module reexports!
The Blobs protocol handler now takes an Endpoint, since that was needed to implement one of the functions.
Change checklist