Filament Comments Laravel Package

Getting Started

This release (3.0.0) is primarily an ecosystem-alignment release: it adds Filament 5 support and ships a fix for the Counter component. Treat it as the version you install on a Filament 5 panel; if you are still on Filament 4, stay on the 2.x line.

Minimal steps:

composer require <vendor>/<package>:"^3.0"
php artisan vendor:publish --tag="<package>-config"   # if the package ships config/views
php artisan migrate                                  # only if the package has migrations

1. Look first at composer.json of the package — confirm the filament/filament constraint is ^5.0. That single line decides whether the upgrade is even possible in your app.
2. Register the plugin in your panel provider (->plugins([...])) if the package exposes a Plugin/PluginInterface class; Filament 5 kept the plugin registration contract, so this is usually a no-op change.
3. First use case: drop the Counter into a dashboard or widget area and confirm it renders and increments. Because 3.0.0 explicitly fixes the Counter, this is also your smoke test — if the count is wrong here, you have a genuine bug rather than an upgrade artefact.

Before touching your app, run the upgrade in a branch and execute composer update --with-all-dependencies — a Filament major bump almost never resolves cleanly with composer update <package> alone.

Implementation Patterns

Pin the pair, not the package. Filament 5 support means the package version and the framework version are now coupled. In composer.json, constrain both so a future composer update cannot silently pull a Filament 5 package into a Filament 4 app:

"filament/filament": "^5.0",
"<vendor>/<package>": "^3.0"

Stage the Filament upgrade behind the package bump. The practical workflow:

1. Upgrade Filament 4 → 5 first, fix your own resources/pages.
2. Then bump this package to ^3.0 and re-run the panel.
3. Only then re-enable any Counter usage you had commented out while debugging — otherwise you cannot tell whether a broken counter is your code or the package.

Counter as a reusable display primitive. The typical day-to-day usage is a stat or KPI block: point it at a model query or closure, give it a label, and place it in a widget or resource page. Wrap it in your own Blade partial or a small Stat wrapper class rather than scattering raw component calls across views — that gives you one place to adjust when the component's API shifts in a future major.

Test the counter as behaviour, not markup. Livewire component tests are the highest-value pattern here, especially since this release contains a counting fix:

Livewire::test(MyDashboard::class)
    ->assertSee('42');           // the computed total
// then create/delete a record and re-assert

A regression test that asserts the value changes after a model event is what would have caught the bug fixed in 3.0.0.

Integration tip: if the Counter aggregates over an Eloquent query, keep the query in a dedicated method or scope so the same logic can be reused by the widget, by an API endpoint, and by the test. Counters that embed query building inline are the ones that drift from the source of truth.

Gotchas and Tips

• This is a major version bump for a reason. Even though the notes read like a feature addition, 3.0.0 signals a Filament major. Assume breaking changes inherited from Filament 5 (view/schema APIs, asset and CSS pipeline changes, deprecated methods) rather than from this package's own surface. Read the Filament 5 upgrade guide, not just these two lines.
• The Counter fix may change visible output. If your app had tests asserting a specific number that was actually wrong, they will now fail correctly. Investigate before adjusting expectations — do not blanket-update snapshots.
• Check for a config/asset republish. After vendor:publish, diff the published config and any compiled CSS/JS against what you had. Stale published views are the most common cause of "the upgrade did nothing".
• Clear aggressively when debugging: php artisan filament:clear-cached-components, view:clear, config:clear, and rebuild assets. Filament caches component discovery, and a stale cache can mask whether the new version is even loaded. Verify with composer show <vendor>/<package>.
• Polling/refresh intervals on counters are easy to misconfigure — a counter that appears frozen is often a too-long refresh interval or a cached query, not the fixed bug reappearing. Check the config default plus any cache TTL you wrapped around the aggregate.
• Extension points: prefer the package's published views and config over subclassing internals. If you need custom formatting, do it in your own wrapper component so a future 3.x patch cannot break your formatting logic.
• If you cannot upgrade yet, pin ^2.0 explicitly and add a note to your upgrade backlog; an unpinned constraint will eventually resolve to 3.x and break the panel at the worst possible moment.