refactor(lib): keep the actors inside the crate and mark the growing enums

Every release since 14 has been a major, because the actor mailboxes,
the share index's struct and the CLI's command enum were all exhaustive
public API: adding a peer message, a scanned field or a subcommand read
as a breaking change to the library. The actors, dispatcher, peer
plumbing and download store are how the client is built, not what a host
programs against, so they move inside the crate; PeerMessage, SharedFile
and the CLI command enums are non-exhaustive; ConnectionType is
re-exported at the root for the one thing hosts used it for. A one-time
break so that the next additions are not.
This commit is contained in:
Michel de Graaf
2026-09-08 01:45:02 +02:00
parent f6423a2ed6
commit 07dd163156
7 changed files with 26 additions and 12 deletions
+2 -3
View File
@@ -3,10 +3,9 @@ pub mod listen;
pub mod upload_peer;
// Export actor types
pub use crate::actor::peer_actor::{PeerActor, PeerMessage};
pub use crate::actor::peer_registry::PeerRegistry;
pub use crate::actor::peer_actor::PeerMessage;
pub(crate) use download_peer::part_path_of;
pub use download_peer::part_path_of;
pub use download_peer::{DownloadError, DownloadPeer};
use crate::message::Message;