Custom theme colors don't work

Z3d0X / filament-logger

Extensible activity logger for filament that works out-of-the-box.

MIT License

287 stars 42 forks source link

Custom theme colors don't work #23

Closed Random72IsTaken closed 2 years ago

Random72IsTaken commented 2 years ago

When Filament is customized with a custom style and colors, the package doesn't account for them. That is, if my theme's color for danger is Tailwind's red, the package still accounts for the default theme color of gray or something.

I think listening to a FilamentServed event - if there is one - would help to identify if its $theme isn't null, and therefore would be injected as a style too.

Z3d0X commented 2 years ago

Color functionality is determined by Badge Column.

By default the following are supported: primary, secondary, success, warning or danger.

However if you look at Badge Column's View, it indicates that, you may also pass custom CSS classes (eg: text-blue-700 bg-blue-500/10). Bear in mind in this case you are responsible to ensure styles for these classes are loaded.