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
First, I want to thank you for providing comprehensive examples for AG Grid integration with various frameworks. The examples have been incredibly helpful in getting started with AG Grid.
However, I've noticed that in the Next.js examples, the ModuleRegistry and LicenseManager are initialized separately for each grid component. This approach can be problematic when dealing with multiple grids in a single application, which is a common use case for many websites.
For example, in a dashboard application, you might have:
A data grid showing user activity
Another grid displaying transaction history
A third grid showing system logs
Currently, each grid component would need to initialize its own ModuleRegistry and LicenseManager, which isn't ideal for maintaining a single source of truth and could potentially lead to initialization conflicts.
Could you provide guidance or update the documentation to show the recommended approach for:
Setting up a shared ModuleRegistry that can be used across multiple grid instances
Initializing the LicenseManager once for the entire application
Properly handling this setup specifically in the Next.js app router environment
This would be particularly valuable for enterprise applications where multiple grids are the norm rather than the exception.
Thank you for your consideration!
The text was updated successfully, but these errors were encountered:
First, I want to thank you for providing comprehensive examples for AG Grid integration with various frameworks. The examples have been incredibly helpful in getting started with AG Grid.
However, I've noticed that in the Next.js examples, the ModuleRegistry and LicenseManager are initialized separately for each grid component. This approach can be problematic when dealing with multiple grids in a single application, which is a common use case for many websites.
For example, in a dashboard application, you might have:
Currently, each grid component would need to initialize its own ModuleRegistry and LicenseManager, which isn't ideal for maintaining a single source of truth and could potentially lead to initialization conflicts.
Could you provide guidance or update the documentation to show the recommended approach for:
This would be particularly valuable for enterprise applications where multiple grids are the norm rather than the exception.
Thank you for your consideration!
The text was updated successfully, but these errors were encountered: