Lazy Loading activitylog.css to Prevent Unnecessary Conflicts and Asset Overload #48
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces the loadedOnRequest() method to prevent the activitylog.css file from being loaded automatically. This change follows the official Filament documentation for lazy-loading assets.
Problem:
The current implementation injects activitylog.css globally, wherever the @filamentStyles directive is used. This includes the admin panel, custom pages, and any Livewire or normal Blade pages. As a result, it leads to:
Solution:
By applying the loadedOnRequest() method, we ensure that activitylog.css is only loaded when explicitly requested, reducing unwanted style conflicts and improving asset performance.