Struct Stack 

pub struct Stack<S, K = String>
where
    S: SignalRw<Vec<K>>,
    K: Route,
{ /* private fields */ }

A push/pop navigation stack whose contents are an app-owned Signal<Vec<K>> (the path above the root). Day reconciles the native stack to the path; the native back button writes the pop back into it (docs/navigation.md).

The key type is any Route: String for raw keys, or a typed enum whose variants can carry data — the destination builder then receives the typed value, and an absolute navigate("…/item-42") parses each segment via Route::from_key (rejecting segments that don’t parse; String accepts everything).

let path = Signal::new(Vec::<Drill>::new());
stack(path.clone(), home_view).destination(|d: &Drill| detail_view(d))
// push:  path.update(|p| p.push(Drill::Item { id: 42 }));

Implementations

impl<K, S> Stack<S, K>

where K: Route, S: SignalRw<Vec<K>>,

pub fn title<M>(self, t: impl IntoText<M>) -> Stack<S, K>

pub fn bar_action<M>( self, icon: impl Into<ImageName>, label: impl IntoText<M>, action: impl Fn() + 'static, ) -> Stack<S, K>

Add a trailing action button to the navigation bar, for the toolkits with no window toolbar (the phones and HarmonyOS): an upper-right bar button drawn with the bundled icon that runs action (docs/navigation.md). Mirrors Selector::bar_action; ignored on desktop.

pub fn destination<P>(self, build: impl Fn(&K) -> P + 'static) -> Stack<S, K>

where P: Piece,

Build the view for a pushed key (&String for raw keys, the typed value otherwise).

pub fn on_back( self, guard: impl Fn(BackRequest) -> BackResponse + 'static, ) -> Stack<S, K>

Intercept the back affordance (docs/navigation.md). The guard runs for every native back gesture/button and nav_back while the stack is above its root; it returns BackResponse::Proceed to pop now or BackResponse::Handled to consume the back (stash the BackRequest and call BackRequest::proceed later). Programmatic path writes are never guarded. While a guard is armed the toolkit stops auto-popping on a native gesture and routes the back through Day instead (NavPatch::GuardTop).

pub fn restore(self, key: impl Into<String>) -> Stack<S, K>

Remember the pushed path across launches (docs/navigation.md). On every change the path’s keys are /-joined and saved under key; at build the saved path is parsed back (each segment via Route::from_key) and restored — so the app reopens exactly where the user left off, including after an Android process death — unless a launch deep link is pending, which wins. Restore is a no-op until the app installs a store (e.g. day_part_prefs::install_nav_store); a saved path with a segment that no longer parses is ignored whole.

Trait Implementations

impl<K, S> Piece for Stack<S, K>

where K: Route, S: SignalRw<Vec<K>>,

fn build(self, cx: &mut BuildCx) -> RNode