You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 28, 2023. It is now read-only.
We'd like to add a new API to instantiate individual pages without having to load a flow (but still allowing to run a flow side-by-side).
The new API should be available as laxar.bootstrap( ... ).page( ref, domContainer ), and support chaining of .flow(), .bootstrap() or other .page() calls.
To allow for this feature, we need to do (at least) the following:
make sure IDs (widgets / event bus subscribers, axId) are generated without conflict if e.g. the same page is instantiated twice,
isolate begin/endLifecycle events (and probably also the initial didChangeLocale) across pages, by having a dedicated "event bus view" for each page, which uses some kind of "source token" with each event to determine its isolation context,
for this, we need to mangle the bootstrapping item IDs into the generated widget IDs.
The text was updated successfully, but these errors were encountered:
We'd like to add a new API to instantiate individual pages without having to load a flow (but still allowing to run a flow side-by-side).
The new API should be available as
laxar.bootstrap( ... ).page( ref, domContainer )
, and support chaining of.flow()
,.bootstrap()
or other.page()
calls.To allow for this feature, we need to do (at least) the following:
axId
) are generated without conflict if e.g. the same page is instantiated twice,begin/endLifecycle
events (and probably also the initialdidChangeLocale
) across pages, by having a dedicated "event bus view" for each page, which uses some kind of "source token" with each event to determine its isolation context,The text was updated successfully, but these errors were encountered: