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
I'm loading multiple microfrontends using SingleSpa. Each microfrontend initializes its own instance of ModelManager using the following code:
ModelManager.initializeAsync({
path: 'path',
modelClient: new ModelClient('url'),
})
The issue is that when the page is loaded, the AEM data is correctly attached to one microfrontend but not to the others. This behavior seems to occur randomly and is associated with the last microfrontend that was loaded.
Package version
1.5.0
To Reproduce
Page initial load
Expected behavior
To see the AEM data correctly attached to each microfrontend
Screenshots
N/A
Additional context
I'm assuming the model is being overwritten by the most recent ModelManager.initializeAsync call
The text was updated successfully, but these errors were encountered:
Describe the bug
I'm loading multiple microfrontends using SingleSpa. Each microfrontend initializes its own instance of ModelManager using the following code:
The issue is that when the page is loaded, the AEM data is correctly attached to one microfrontend but not to the others. This behavior seems to occur randomly and is associated with the last microfrontend that was loaded.
Package version
1.5.0
To Reproduce
Page initial load
Expected behavior
To see the AEM data correctly attached to each microfrontend
Screenshots
N/A
Additional context
I'm assuming the model is being overwritten by the most recent
ModelManager.initializeAsync
callThe text was updated successfully, but these errors were encountered: