I’m attempting to update our Aurelia application to use the current v1 packages and in doing so have discovered a change in the execution order that is causing issues.
The entry point module is called MainFrame which extends a base class called MainFrameBase. Mainframe contains the configureRouter() function. The ‘home’ route is configured to be the AppDashboardDialog module.
The current application order of execution is as follows:
INFO [aurelia] Aurelia Started
DEBUG [app] MainFrame base constructor (ViewElementBase) entered
INFO [app] MainFrameBase entered
INFO [app] MainFrame entered
DEBUG [app] Mainframe.activate entered
DEBUG [templating] importing resources for mainframe.html
INFO [app] configureRouter entered
INFO [app] StaticRoutes contains 1 routes
INFO [app] DialogRoutes contains 464 routes
INFO [app] TestRoutes contains 6 routes
INFO [app] RouteMap (Static + Dialog) contains 471 routes
INFO [app] MainFrameBase.bind entered
DEBUG [app] AppDashboardDialog base constructor (ViewElementBase) entered
DEBUG [app] Dialog constructor entered
DEBUG [app] SimpleDialog constructor entered
INFO [app] AppDashboardDialog constructor entered
INFO [app] Dialog.activate entered
DEBUG [app] Dialog.preActivate entered
DEBUG [app] Dialog.postActivate entered
DEBUG [app] Dialog.bind entered
DEBUG [app] Dialog.postAttached()
The new application order of execution is as follows:
INFO [aurelia] Aurelia Started
DEBUG [app] MainFrame base constructor (ViewElementBase) entered
INFO [app] MainFrameBase entered
INFO [app] MainFrame entered
DEBUG [app] Mainframe.activate entered
DEBUG [templating] importing resources for mainframe.html
INFO [app] configureRouter entered
INFO [app] StaticRoutes contains 1 routes
INFO [app] DialogRoutes contains 460 routes
INFO [app] TestRoutes contains 6 routes
INFO [app] RouteMap (Static + Dialog) contains 467 routes
**** New sequence appears to trigger the routing to the 'home' dialog before completion of the MainFrameBase class.
DEBUG [app] AppDashboardDialog base constructor (ViewElementBase) entered
DEBUG [app] Dialog constructor entered
DEBUG [app] SimpleDialog constructor entered
INFO [app] AppDashboardDialog constructor entered
INFO [app] Dialog.activate entered
DEBUG [app] Dialog.preActivate entered
DEBUG [app] Dialog.postActivate entered
DEBUG [app] Dialog.bind entered
INFO [app] MainFrameBase.bind entered
INFO [app] MainFrameBase.attached entered
DEBUG [app] Dialog.postAttached()
The code in the Dashboard dialog relies on the completion of the MainFrame and MainFrameBase classes before the route is triggered. The change in execution sequence is causing downstream issues for the Dashboard dialog.
I’m more than happy to provide further information, I’m just not sure what is relevant to provide at this stage.
Any help would be much appreciated.