Michael Kurze
Michael Kurze
Hello, we use jjv for JSON schema validation and instantiation, and are mostly very happy with it. Recently we stumbled upon the effects of https://github.com/acornejo/jjv/pull/51 -- since that has been...
I'm using a setup where there is a "vendor" bundle containing libraries such as Angular, and an "app" bundle containing our project specific code. In this case, it seems that...
The laxar-dox doc generator uses a very outdated version of dox that relies on outdated dependencies. This dependency is responsible for almost all security audit issues reported in the repo....
Currently, navigateRequests cannot be intercepted. And when clicking a link, the modified place parameter will be published without any prior warning. Widgets should be able to indicate their "busy" status...
For the future, we'd like to be able to allow for simple integration of the LaxarJS flow with external routing libraries. Use Cases: - seamlessly integrate with arbitrary existing applications...
Currently, the validation of the flow definition is probably too permissive: for example, it would be possible to define a place named `_`.
A bootstrapped laxar instance should offer a simple way to load and instantiate widgets without flow or pages, e.g. to simplify integration into existing applications. Details TBD
Widgets should be allowed to request an axBootstrap injection in order to create their own widgets/pages/... sharing the parent applications adapters, injections and so on.
It should be possible to completely tear down a LaxarJS bootstrapping instance through a destroy() method. Possibly we should allow for an optional technology adapter hook to perform technology-specific cleanup.
Currently, all application artifacts (widgets, pages, flows, layouts...) are prebundled using the laxar-loader for webpack. Sometimes it is desirable to add or replace individual items, e.g. to load user-defined pages...