Build the router's navigation effect for a native application.
This is the other half of the loop. The router resolves a destination into a path and
hands it here; this pushes it back into the same source the adapter listens to, so the
kernel resolves the new route exactly as it resolved the first one. The browser closes
this loop through the History API and a window event; a native application closes it
through the source it already owns, and needs no History API at all.
replace is carried in the metadata rather than acted upon: whether replacing an entry
means anything is a question for the view layer's navigation stack, not for the adapter.
Build the router's navigation effect for a native application.
This is the other half of the loop. The router resolves a destination into a path and hands it here; this pushes it back into the same source the adapter listens to, so the kernel resolves the new route exactly as it resolved the first one. The browser closes this loop through the History API and a window event; a native application closes it through the source it already owns, and needs no History API at all.
replaceis carried in the metadata rather than acted upon: whether replacing an entry means anything is a question for the view layer's navigation stack, not for the adapter.