- What is jeffersongoncalves/filament-additional-information used for?
- It provides a reusable Filament infolist section that displays created_at and updated_at timestamps and can optionally render additional timestamp entries via make(). It is a presentation-layer convenience for Laravel admin panels built with Filament, not a persistence or audit-log package. It does not add migrations, models, or domain logic.
- Which Filament versions does this package support?
- The provided evaluation does not confirm exact Composer constraints; it notes that Filament v3-style infolists are the assumed target and that v4 compatibility is unproven. Check composer.json for the Filament, Laravel, PHP, and Livewire constraints before installing. Treat Filament v4 support as requiring a branch test.
- How do I install filament-additional-information in a Laravel app?
- Install via Composer with composer require jeffersongoncalves/filament-additional-information, then use the section in a Filament resource infolist schema. The assessment indicates a small install surface with no obvious service provider, config publishing, or asset compilation steps. Verify auto-discovery or manual panel registration against the package's composer.json and README.
- How do I add the additional information section to a Filament infolist?
- Add the package's Section or factory to the resource's infolist schema, typically as AdditionalInformation::make(), alongside your TextEntry fields. Ensure the entry names match the model's actual timestamp attributes, such as created_at and updated_at. If your model hides or renames those attributes, adjust the schema accordingly.
- Does it respect Laravel's app timezone and date formatting?
- The package is a thin wrapper over Filament Section and TextEntry APIs, so timezone and formatting behavior likely depends on Filament and your application configuration. The evaluation flags hidden assumptions around timezone, date formatting, localization, and null handling as risks. Test with a non-UTC app timezone and with null timestamps before relying on it in production.
- Can I customize labels, hide null timestamps, or show relative times?
- The API is described as intentionally narrow, with created_at and updated_at plus optional additional timestamp entries via make(). The provided context does not confirm options for custom labels, since() relative display, or hiding nulls. If those controls are required, inspect the class API or consider a local wrapper around Filament's TextEntry.
- Is this package translatable or localized?
- The assessment does not confirm built-in translation files or localized labels. Because it renders Filament infolist entries, any localization would likely come from your Filament translations or custom labels. Verify label text and date formatting in each target locale before adopting it broadly.
- Does the package have tests or CI?
- The metadata provided does not show a visible test suite or CI signal. That is a meaningful risk for a small, single-maintainer package, even though the code surface is tiny. Run your own staging render checks, including null timestamps and non-UTC timezones, before merging.
- What are the alternatives to using this package?
- The main alternative is to write roughly 20 lines of inline Filament TextEntry code or copy the section pattern into your own App\Filament\Infolists namespace. Vendoring the pattern removes the dependency while preserving a consistent timestamp block. For non-Filament Laravel apps, this package has no applicability.
- Is it safe to use in production and how should I manage maintenance risk?
- Supply-chain risk is modest because the code surface is tiny and MIT-licensed, but it is unreviewed and has only one star and no dependents. Pin an exact version, isolate usage behind a local wrapper class, and document the decision in your dependency register. Roll out to one resource in staging first and treat Filament v4 compatibility as unproven.