- How do I install dillingham/nova-grouped-field in a Laravel Nova application?
- Install it with a standard composer require and then register the field inside your Nova resource definition, nesting the fields you want rendered together. There is no service provider wiring, queue, cron job, or infrastructure change involved. A Nova-fluent developer can have it rendering in under an hour.
- Does nova-grouped-field support Nova 4 or Nova 5 and PHP 8?
- The package does not declare a supported-version matrix, and the last release (0.11) dates to January 2020, so compatibility with modern Nova majors and PHP 8.x is unverified. Because the field depends on Nova's internal field API, which has shifted across majors, confirm it actually renders on your Nova version before adopting it. Treat version compatibility as the first thing you test, not an assumption.
- How does nova-grouped-field handle empty fields and stray separators?
- Release 0.11 added separator suppression on empty fields, so a partially filled record no longer renders as something like Acme — — Amsterdam. That fix is the strongest operational reason to take the dependency instead of hand-rolling the formatting. Still verify all-empty groups, since blank versus placeholder versus stray separator behavior is worth confirming in your own resources.
- Can I use nova-grouped-field to combine multiple columns in a Nova index view?
- Yes, its primary purpose is merging several related record attributes into a single displayed column with a configurable separator, which works for index listings and detail views. Separator escaping can differ between the index and detail renderers, so diff both contexts against your incumbent output. It is a display-only field and does not store or transform data.
- What are the alternatives to dillingham/nova-grouped-field?
- You can keep duplicated Text::make() columns, write a Text field with a displayUsing() closure, or build the equivalent field in-house, since the package is roughly 50 lines of formatting code. If you are not committed to Nova, Filament ships a first-party stacked TextColumn for the same job. The grouped field is a convenience for reducing column sprawl, not a new capability.
- Is dillingham/nova-grouped-field still maintained?
- The package has a single maintainer, around 40 stars, zero dependents, and its last release was 2020-01-12. The risk is silence rather than active churn, so expect no fixes for new Nova majors unless you make them. Fork-and-vendor cost is low because the code surface is small.
- Is it safe to depend on a pre-1.0 package like nova-grouped-field in production?
- By 0.x convention, minor version bumps may carry breaking changes, so pin the exact version you validate. Rollback is trivially safe because the field is display-only: there is no data migration and removal is a one-line change in the resource definition. Keep your previous column definitions in version control as the rollback artifact.
- Does nova-grouped-field support date formatting and line-break separators?
- Release 0.11 added date formatting and line-break separator support alongside the empty-field fix. Date formatting applied to non-Carbon values is an unverified behavior, so test it against any attribute that is not a real date. Separator escaping (newline versus <br> versus plain text) can also differ between index and detail renderers, surfacing as visual bugs rather than exceptions.
- Do I need configuration or migrations to use nova-grouped-field?
- No configuration file and no migrations are required; you swap the existing Text::make() columns or displayUsing() closure for one grouped field and diff the rendered output. The recommended migration path is incremental, one resource at a time, then deleting the old columns. Nothing touches your domain model, persistence layer, or customer-facing surface.
- Can nova-grouped-field render interactive grouped cells, like per-segment links or badges?
- No. It is display-only, so per-segment links, badges, copy-to-clipboard, and inline-edit interactions hit the package ceiling immediately. If you need interactive grouped cells, build a custom Nova field instead. The grouped field is appropriate only where you want cleaner rendering of related attributes in admin listings.