- How do I install awcodes/filament-badgeable-column in a Laravel app?
- Install it with composer require awcodes/filament-badgeable-column. Then add a Tailwind @source line pointing at the package views, for example @source '../../../../vendor/awcodes/filament-badgeable-column/resources/**/*.blade.php';, either in your custom Filament theme CSS or in your app CSS when using the standalone Tables package. There is no service provider to register, no config file to publish and no migrations to run. Rebuild your front-end assets and the badge styles are compiled into your theme.
- Which Filament versions does filament-badgeable-column support?
- Versions are aligned to Filament majors: package 1.x targets Filament 2.x, 2.x targets Filament 3.x, 3.x targets Filament 4.x, and 4.x supports both Filament 4.x and 5.x. That mapping makes version pinning mechanical rather than a judgement call in composer.json. Check the compatibility table in the README before upgrading either side, because the package tracks Filament internals closely and should move in lockstep with Filament minors, not just majors.
- Do I need a custom Filament theme to use BadgeableColumn?
- Yes, if you are using Filament Panels you must have a custom theme set up per the Filament styling docs before adding the @source directive. The package ships Blade views whose utility classes only exist once your theme build scans them. Standalone Tables users can add the same @source line to their app CSS instead. This makes your theme build pipeline a hard dependency, so confirm the rebuild runs in CI before adopting.
- How do I add prefix and suffix badges to a Filament table column?
- Swap the column class and pass badge arrays: BadgeableColumn::make('name')->prefixBadges([...])->suffixBadges([...]), where each Badge is built with Awcodes\BadgeableColumn\Components\Badge::make('key'). Badges accept label(), color(), icon() and visibility methods, and standard column methods such as searchable() and sortable() still chain normally. Because it subclasses Filament's column primitive, the change is additive and can be reverted in a single pull request.
- Does the package work with Filament infolist entries, or tables only?
- It supports both. BadgeableColumn decorates table columns and BadgeableEntry decorates infolist entries, with infolist support added in package version 2.2.0. If you only need tables, the Tables-only configuration is explicitly supported. Confirm entry parity on the package major that matches your Filament version before relying on it across both surfaces.
- Is BadgeableColumn better than the native TextColumn::badge() method?
- Not always. Native TextColumn::badge(), description() and icon() cover the common case of a single status badge attached to a value, with no extra dependency. Reach for BadgeableColumn when you genuinely need several badges rendered as affixes around a cell, or when you want badges on infolist entries. If one badge per cell is enough, skipping the package keeps your theme pipeline and upgrade surface smaller.
- Can badge labels and colors change per record?
- Yes. label(), color() and visible() accept closures that receive the $record, so you can match on a status column or build colors from any model attribute, using Filament color tokens such as success, danger and warning. The same closures can read relationships to build a badge array, for example mapping a topics relation into badges. That flexibility is convenient but easy to abuse, so review where the closures run.
- Do badge closures cause N+1 query problems in Filament tables?
- They can. Because badge closures are evaluated per row and may dereference relationships such as $record->topics->map(...), the package makes N+1 queries easy to write and does nothing to prevent them. Eager load the relationships in your Resource query with with() or withCount() and measure query counts on a realistic page size before shipping. Treat a badge that touches a relation as a schema-level performance decision, not just a styling tweak.
- Why did the namespace change from Awcodes\FilamentBadgeableColumn to Awcodes\BadgeableColumn?
- The namespace was shortened in the v2 to v3 upgrade, so any future major jump crosses a hard breaking change with no compatibility shim. Plan the import rewrite as part of that upgrade rather than assuming a drop-in composer update. Because usage is confined to Resource and Table schema classes, the blast radius of the rename is usually a small, greppable set of files you already own.
- Is filament-badgeable-column safe to use in production?
- It is MIT licensed, presentation-only and has a shallow footprint, so the blast radius is low, but it is maintained by a single author with no commercial SLA and a modest star count. Release history shows repeated fixes chasing Filament internals, so budget for upgrading it alongside Filament minors and cover your tables with basic render tests. Define an exit trigger in advance, such as an unresolved upstream breakage window, and remember the code is small enough to fork and vendor if the package is abandoned.