Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistent Attachment of AEM Data to Multiple Microfrontends Loaded via SingleSpa #102

Open
cbracewell opened this issue Jun 30, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@cbracewell
Copy link

cbracewell commented Jun 30, 2023

Describe the bug

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

@cbracewell cbracewell added the bug Something isn't working label Jun 30, 2023
@cbracewell cbracewell changed the title [bug] Inconsistent Attachment of AEM Data to Multiple Microfrontends Loaded via SingleSpa Jun 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant