Expose `onion_message` items directly rather than via re-exports 2024-01-om-direct-export
authorMatt Corallo <git@bluematt.me>
Wed, 10 Jan 2024 18:27:57 +0000 (18:27 +0000)
committerMatt Corallo <git@bluematt.me>
Wed, 10 Jan 2024 23:50:34 +0000 (23:50 +0000)
commitab66143cb614b54e009152d0c590813a57a409e5
treea196545ee8757ae348eebbe8dac7067208901a38
parentf352d03ee98aed3d940e697fcb09371cfdc3ab15
Expose `onion_message` items directly rather than via re-exports

When we originally added the `onion_message` module, there weren't
a lot of public items in it, and it didn't make a lot of sense to
export the whole sub-module structure publicly. So, instead, we
exported the public items via re-exports directly in the
`onion_message` top-level module. However, as time went on, more
and more things entered the module, which left the top-level module
rather cluttered.

Worse, in 0.0.119, we exposed
`onion_message::messenger::SendSuccess` via the return type of
`send_message`, but forgot to re-export the enum itself, making
it impossible to actually use from external code.

Here we address both issues and simply replace the re-export with
the underlying sub-module structure.
15 files changed:
fuzz/src/chanmon_consistency.rs
fuzz/src/full_stack.rs
fuzz/src/onion_message.rs
lightning/src/blinded_path/message.rs
lightning/src/blinded_path/utils.rs
lightning/src/events/mod.rs
lightning/src/ln/channelmanager.rs
lightning/src/ln/msgs.rs
lightning/src/ln/peer_handler.rs
lightning/src/onion_message/functional_tests.rs
lightning/src/onion_message/messenger.rs
lightning/src/onion_message/mod.rs
lightning/src/onion_message/offers.rs
lightning/src/routing/router.rs
lightning/src/util/test_utils.rs