Skip to content

feat: add Filament icon alias support for UI customization#31

Open
kaungkhantjc wants to merge 6 commits into
relaticle:1.xfrom
kaungkhantjc:1.x
Open

feat: add Filament icon alias support for UI customization#31
kaungkhantjc wants to merge 6 commits into
relaticle:1.xfrom
kaungkhantjc:1.x

Conversation

@kaungkhantjc

@kaungkhantjc kaungkhantjc commented Jun 18, 2026

Copy link
Copy Markdown

Hi there! 👋

First, thank you so much for this very awesome library ❤️! It's incredibly clean, well thought out, and an absolute joy to use.

I am submitting a PR to introduce Filament's built-in Icon Alias feature to the package. This allows us to easily replace the default Heroicons used throughout the package (timeline, relation managers, header actions, operation types) with their own custom icons, entirely avoiding the need to customize every component, publish or override Blade views.

Sample Usage:

Developers can now effortlessly override default icons directly in their service providers:

use Filament\\Support\\Facades\\FilamentIcon;  
use Relaticle\\ActivityLog\\Icons\\ActivityLogIconAlias;

public function boot(): void  
{  
    FilamentIcon::register([  
        ActivityLogIconAlias::ACTION_ICON => 'heroicon-o-sparkles',  
        ActivityLogIconAlias::TIMELINE_EMPTY => 'heroicon-o-face-frown',  
    ]);  
}

Changes Included:

  • Added ActivityLogIconAlias class containing constants for all customizable icons.
  • Registered default icons natively using FilamentIcon::register() in the ActivityLogServiceProvider > packageBooted() method.
  • Updated all Blade views and UI classes to resolve icons via <x-filament::icon :alias="..."> and FilamentIcon::resolve().
  • Added comprehensive Pest tests (IconAliasTest.php) to ensure defaults register correctly and can be overridden.
  • Added a new "Icon Aliases" Nuxt Docus page, and added the feature to the README.md list.

All tests are passing locally! Please let me know if you need any tweaks or changes. Thanks again for your hard work on this!

@kaungkhantjc

Copy link
Copy Markdown
Author

Hi @AsmitNepali , just a quick heads-up. I realized after submitting that I accidentally committed these changes directly to my fork's 1.x branch instead of creating a separate feature branch.

The PR should still merge perfectly, but please let me know if you need me to close this and re-submit it from a feature branch instead. Thanks!

@AsmitNepali

Copy link
Copy Markdown
Collaborator

Hi @kaungkhantjc
Sure, please send it from a feature branch. That will make it easier to review and keep the 1.x branch clean. Thanks!

@AsmitNepali AsmitNepali self-requested a review June 21, 2026 13:45
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

Successfully merging this pull request may close these issues.

2 participants