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

Handling BladeProvider in Module Federation #2321

Open
snitin315 opened this issue Jul 25, 2024 · 0 comments
Open

Handling BladeProvider in Module Federation #2321

snitin315 opened this issue Jul 25, 2024 · 0 comments

Comments

@snitin315
Copy link
Member

Summary

In a module-federated application, both the remote and host applications require the BladeProvider to provide theme context. However, the remote app should inherit the theme context from the host if the host is already wrapped in BladeProvider. Currently, an error occurs if the remote app is not wrapped within the provider, indicating that the context is not being shared correctly.

Problem

When the host application is wrapped in <BladeProvider />, the imported remote application should not need to use <BladeProvider /> again. Despite this, an error is thrown if the remote app is not wrapped within the provider.

Steps to reproduce:

Expected Behavior

The context provided by BladeProvider in the host application should be available to the remote application, eliminating the need for the remote app to include its own BladeProvider

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant