- What is awcodes/trov-components used for in Laravel and Filament?
- It is a small Blade-component library that extends Filament Admin with reusable UI components and form fields. It sits at the presentation layer only, so it adds no database schema, queues, or service-provider overhead. Developers use it to assemble common admin interface elements faster with Composer-only installation.
- Is awcodes/trov-components still maintained after Filament core added Section?
- The technical evaluation flags upstream absorption as a continuity risk: the headline Panel component was absorbed into Filament core in v0.3.0. That does not prove abandonment, but the assessment recommends checking commit cadence, issue responsiveness, and maintainer count before relying on future releases. It specifically warns not to plan on v0.4.x existing.
- How do I migrate from Trov Components Panel to Filament Section in v0.3.0?
- Inventory every <x-...-panel> reference across app code, published Blade views, and vendor-published stubs. Confirm your installed Filament version ships Section and that its API covers every attribute or prop you currently pass to Panel, because parity is assumed but not guaranteed. Then replace the component tags, remove the Trov import or namespace references, and visually QA the affected admin screens.
- Does awcodes/trov-components support Laravel 11 and Filament v3?
- The supplied context does not list exact Laravel or Filament version constraints, so verify the package's composer.json and README before installing. The evaluation does note that v0.3.0 has a Filament major/minor requirement that must align with your pinned Filament version. It also says the package is native to Laravel and Filament with no impedance mismatch, but that is not a version-support guarantee.
- How do I install awcodes/trov-components with Composer?
- Install it as a normal Composer dependency in your Laravel application; the evaluation describes integration as mechanically trivial with no infrastructure, schema, queue, or cache implications. Because it is a Blade-level Filament extension, no significant service provider configuration is expected. After installing, confirm the component tags resolve in your admin views and that your Filament version matches the package requirement.
- Why did my Filament admin break after updating awcodes/trov-components to v0.3.0?
- v0.3.0 removed the Panel component because its functionality moved into Filament core, so any remaining <x-...-panel> tag will fail at Blade render time. The failure appears when an admin screen renders, not at application boot, which means unit tests may pass while the UI breaks. Replace Panel references with Filament's Section component and check for props that Section may not support.
- Should I remove awcodes/trov-components if I only used the Panel component?
- If Panel was your only usage, the technical evaluation recommends deprecation and removal rather than upgrade. Once Filament core ships Section, keeping the dependency adds supply-chain and upgrade surface without clear value. Sequence removal as a standalone PR after inventorying call sites and confirming no other Trov components are in use.
- What components or fields does awcodes/trov-components provide besides Panel?
- The overview describes a set of reusable Trov UI components and fields for Filament Admin, but the supplied context does not enumerate them. The evaluation explicitly asks whether the package exposes form fields, table columns, actions, or themes that your application depends on. You must audit actual usage before deciding between removal and a ^0.2 pin.
- Can I pin awcodes/trov-components to ^0.2 as a temporary fallback?
- Yes, the evaluation lists pinning ^0.2 explicitly as a fallback if you still need other components. Document the rationale and open a replacement ticket, because v0.3.0's breaking change shipped on a 0.x minor bump. Avoid loose constraints such as >=0.2 or *, which could pull v0.3.0 automatically and break CI or admin rendering.
- How should I test Filament admin screens for broken Trov components?
- Add render-level coverage for affected admin pages, because Blade component removal fails at render time rather than boot time. Do not rely on a green build alone if Panel props may behave differently under Section; the evaluation calls for visual QA of impacted screens. Also gate automated dependency bumps so a Renovate or Dependabot PR cannot land v0.3.0 unassisted.