Dan Harrin
Dan Harrin
I'm interested now... can we somehow refactor `BooleanColumn` to extend `IconColumn`?
Gonna close this, many merge conflicts so it would be easier to do the work on a new branch anyway
> Isn't it too similiar to the current layout? You can achieve layout close to this with `formatStateUsing`, but I suppose change will bring more clean api. > > What...
Well @studiowizjo... I take back what I said. I made grid cards 😂
Confirmed, can only fix in v3 when we switch to a different markdown editor though. The reason why this doesn't work is because we need a `wire:ignore` to wrap around...
I also agree with @themahdavi and @ryangjchandler 😬 Just because an icon was designed for a specific size doesn't mean it doesnt work in other styles, because it's all contextual....
So how does it look if we work out how to make the outlined icons work at the larger size?
We should have an IconsRepository class that is bound to the container & registers icons for all parts of Filament
I basically just want a way where you can call stuff from a service provider ```php Icon::for('tables::search') ->is('heroicon-o-search') ->size('w-5 h-5') ```
Because it's important to be able to change icon width as well as swap icons out