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
By now TerrificJS does only take care of instantiating the correct modules and skins. It does not provide a mechanism to lazy load modules on a granular level. Most of the time its assumed, that all module classes exists on page load.
With the more descriptive approach described in #40 TerrificJS is able to introduce granular loading out-of-the-box. Its even possible to only lazy load modules that do not exist on page load.
The mechanism will work as follows:
Check whether Tc.Module.Xyz is existent during the bootstrap
2a. If yes -> do nothing
2b. If no -> lazy load Tc.Module.Xzy
Bootstrap modules as normal
The text was updated successfully, but these errors were encountered:
As lazy loading is not used in every project, we do not want to blow up the code and lose TerrificJS micro focus due to this feature. Moreover the lazy loading part can be solved in many different ways – e.g. by using the AMD pattern or by simple script injection – and we do not want to introduce an opinionated way to solve this issue.
Nonetheless with the introduction of lifecycle events #53 it should be easy to implement a lazy loading mechanism for your project.
By now TerrificJS does only take care of instantiating the correct modules and skins. It does not provide a mechanism to lazy load modules on a granular level. Most of the time its assumed, that all module classes exists on page load.
With the more descriptive approach described in #40 TerrificJS is able to introduce granular loading out-of-the-box. Its even possible to only lazy load modules that do not exist on page load.
The mechanism will work as follows:
2a. If yes -> do nothing
2b. If no -> lazy load Tc.Module.Xzy
The text was updated successfully, but these errors were encountered: