From 7ab7928415cdc2363f9dc98f8fda8be3a0a67566 Mon Sep 17 00:00:00 2001 From: jezza Date: Tue, 20 Jan 2026 09:41:31 +0100 Subject: [PATCH] fix(rumqttd): Expose bridge module and Event type. The bridge module wasn't exposed, which meant the only way to create a bridge was to use the Broker directly. The event type is also on a public API via the Router but isn't exposed, meaning you can't name this type. Signed off: Jeremy Barrow --- rumqttd/CHANGELOG.md | 2 ++ rumqttd/src/lib.rs | 5 ++++- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/rumqttd/CHANGELOG.md b/rumqttd/CHANGELOG.md index 70127bb7f..789575eb2 100644 --- a/rumqttd/CHANGELOG.md +++ b/rumqttd/CHANGELOG.md @@ -9,6 +9,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 ### Added ### Changed +- Export the `Event` type, so the Router's Sender can be used. +- Export the `bridge` module so a bridge can be constructed directly, rather than using the `Broker`. ### Deprecated ### Removed ### Fixed diff --git a/rumqttd/src/lib.rs b/rumqttd/src/lib.rs index d32d4b603..d46661c62 100644 --- a/rumqttd/src/lib.rs +++ b/rumqttd/src/lib.rs @@ -19,9 +19,12 @@ use tracing_subscriber::{ }; pub use link::alerts; +pub use link::bridge; pub use link::local; pub use link::meters; -pub use router::{Alert, Forward, IncomingMeter, Meter, Notification, OutgoingMeter, Router}; +pub use router::{ + Alert, Event, Forward, IncomingMeter, Meter, Notification, OutgoingMeter, Router, +}; use segments::Storage; pub use server::{Broker, LinkType, Server};