Michael Kurze
Michael Kurze
_Idea:_ after receiving a navigateRequest or when the user has clicked a link, the flow controller could publish a _confirmNavigationRequest_ with payload attribute `target` (or possbily `place`). Widgets can then...
_To be discussed:_ To intercept navigation for an unbounded time period, the flow controller must disable the eventbus timeout. Possibly we should specify a "magic" option value for publishAndGatherReplies to...
To interrupt navigation (e.g. to display a confirmation dialog), widgets should deny the navigationConfirmationRequest and (after user consent) publish a new navigateRequest. For this to work, the confirmNavigationRequest must contain...
For this, ideally we'd also allow _load_ an artifacts bundle directly from a widget.
@jpommerening I like that that your suggestions allow for a more powerful API. OTOH, I would love to have a bootstrapping API that prevents users from shooting themselves in the...
@alex3683 FYI ^
Oh, and now a neat idea comes to mind, maybe for `v2.1`: ```js const configMain = { /*...*/ }; const artifactsMain = require( 'laxar-loader/artifacts?flow=main&...' ); const nodeMain = document.querySelector( /*...*/...
After some more deliberation, it looks like we're aiming for something like this: ```js import { create } from 'laxar'; const adapters = [ require( 'laxar-react-adapter' ), /*...*/ ]; const...
The necessary preparations (#437) have been made so that we can introduce standalone loading in a minor version to come. Moving this out of the milestone for now, so that...
Depends on #473