Introduce a Reactive Component for Event Consumption in App Navigation

[Basler182]

Problem

using a pure shared flow might risk losing some events due to the fire-and-forget nature of shared flows. This means that the navigator may not be aware if the event it fired was indeed consumed.

Solution

Introduce a reactive component that notifies back the navigator when an event is consumed. This component will ensure that the navigator is aware of the event's consumption status, addressing the potential issue of losing events.

Additional context

No response

Code of Conduct

• I agree to follow this project's Code of Conduct and Contributing Guidelines