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
It would be fantastic if Laravel Pulse offered the ability to publish Blade components from the components folder, similar to how Livewire views can be published. This would significantly simplify customization, allowing developers to adjust elements like headers, spacing, or colors without the need to modify files directly within the vendor directory.
I attempted to publish the files using the following command:
php artisan vendor:publish --tag=pulse-dashboard
However, this only publishes the dashboard view, and it offers limited flexibility for customization within that view.
While it’s possible to manually copy the files from the package and move them to the appropriate folders, this approach still presents challenges. For example, I can't extend from my custom templates, and the global styles applied by Pulse override existing styles, such as fonts, already set in my interface.
A potential solution could be the addition of a publishable tag for Blade components, allowing them to be easily customized and extended—similar to how Laravel Breeze enables styling overrides. This would make Pulse much more flexible and easier to integrate into custom Laravel applications.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
It would be fantastic if Laravel Pulse offered the ability to publish Blade components from the components folder, similar to how Livewire views can be published. This would significantly simplify customization, allowing developers to adjust elements like headers, spacing, or colors without the need to modify files directly within the vendor directory.
I attempted to publish the files using the following command:
php artisan vendor:publish --tag=pulse-dashboard
However, this only publishes the dashboard view, and it offers limited flexibility for customization within that view.
While it’s possible to manually copy the files from the package and move them to the appropriate folders, this approach still presents challenges. For example, I can't extend from my custom templates, and the global styles applied by Pulse override existing styles, such as fonts, already set in my interface.
A potential solution could be the addition of a publishable tag for Blade components, allowing them to be easily customized and extended—similar to how Laravel Breeze enables styling overrides. This would make Pulse much more flexible and easier to integrate into custom Laravel applications.
Beta Was this translation helpful? Give feedback.
All reactions