- How do I install nakukryskin/orchid-repeater-field in a Laravel application?
- Install it with Composer using the package name nakukryskin/orchid-repeater-field, then register the package service provider if your Laravel version does not auto-discover it. After that, publish any Blade views or config the package ships so the repeater field template can render inside your Orchid admin panel. Finally, reference the repeater field class in an Orchid screen definition and confirm the field renders in the browser before wiring up persistence. Because the repository is archived, check the package's composer.json constraints against your locked Orchid and Laravel versions first.
- Which Orchid, Laravel, and PHP versions does this repeater field support?
- The package's supported matrix is defined by the constraints in its composer.json, and since the repository is archived those constraints are likely pinned to older Orchid and Laravel releases. There are no recent compatibility updates, zero dependents, and only limited community validation, so do not assume it works with current Orchid majors. Run a short compatibility spike in a branch against your exact Orchid, Laravel, and PHP versions before committing. If the constraints block installation, expect to relax them in a fork and then verify rendering, validation, and persistence.
- How does the Orchid repeater field store repeatable rows as JSON?
- The package is designed to let you add, sort, and manage repeatable groups of fields in Orchid admin forms and persist those rows as structured JSON, so a single model column can hold the nested data. The technical assessment flags the exact storage mechanism as something to verify, since the code may use a JSON column directly or a custom cast rather than a related table. Confirm the column type and casting behavior in your schema before shipping, especially if the model already contains JSON payloads. Defining an explicit shape for the repeated rows up front protects you from JSON schema drift later.
- Is nakukryskin/orchid-repeater-field still maintained?
- No. The GitHub repository is archived, which means no upstream fixes, no security patches, and no compatibility updates for newer Orchid or Laravel releases. With 59 stars and zero dependents, there is minimal community validation to rely on if something breaks. The MIT license is permissive, so you can fork and maintain it internally, but you should budget ownership from day one. Treating it as a direct Composer dependency without a fork is not operationally sustainable.
- Does the repeater field support nested repeaters, file uploads, or conditional fields?
- The package documentation available here does not confirm support for nested repeaters, file uploads inside repeated rows, or conditional field logic. The technical assessment lists these as open questions that need verification in code rather than assumptions from the package description. If your admin screens depend on any of those behaviors, prototype them in a branch and confirm the Blade rendering and persistence work as expected. For unsupported cases, plan to extend the field in your fork or model the relationship with standard Orchid fields instead.
- How do I validate repeated rows from an Orchid repeater field?
- Validation behavior for nested and repeated fields is one of the gaps the technical assessment flags as undocumented, so read the field class to see what rules it applies and how it maps request keys. In practice you will likely need custom rules in your screen or form request that validate the array structure and each nested key explicitly. Also verify that server-side validation errors render back inside the repeater rows rather than only at the top of the form. Add regression tests for both valid and invalid payloads before rollout.
- Should I use this package or write my own repeater field for Orchid?
- It can reduce custom admin UI work for repeatable field groups if your application already standardizes on Orchid for back-office CRUD screens. However, because the repository is archived, the realistic comparison is between forking this code and building a small field yourself, not between this package and zero maintenance. A contained, well-tested custom field may be cheaper over time than adopting an unmaintained one. Either way, do not introduce Orchid itself just to use a repeater field.
- Can I use this repeater field with Filament, Nova, or plain Laravel forms?
- No. The package extends Orchid's field system specifically, exposing a field class and Blade view that only Orchid screens can consume. It has little or no value outside an application already using the Orchid Platform for admin panels. If you are on Filament or Nova, use that ecosystem's native repeater component instead. For plain Laravel forms, a Livewire or Alpine-based repeater paired with a JSON cast is a more appropriate fit.
- Should I install this package directly or fork it first?
- Fork first. The recommended path is to run a compatibility spike against your target Orchid and Laravel versions, then if viable fork the repository under your organization and pin a tagged version, wiring it in via a Composer VCS or path repository. Publish and review the Blade views, config, and any migrations before integrating it into a single low-risk Orchid screen. Once the fork is stable and covered by tests, you can consider expanding its use. Avoid combining it with other unmaintained Orchid extensions that may also rely on older internals.
- How do I test a repeater field integration in an Orchid admin screen?
- Start with a single low-risk screen and a rollback plan, then add automated tests for rendering, validation, persistence, and edge cases before broadening usage. Cover the field contract: adding rows, reordering rows, saving, reloading the JSON payload, and submitting invalid nested values to confirm error handling. Monitor production for rendering, escaping, and persistence issues after release, since silent validation failures or corrupted JSON payloads are the main blast radius. Because the fork is now owned by your team, these tests are also your regression safety net for future Orchid upgrades.