- What is royduin/laravel-nova-field-dynamic-select used for?
- It adds dynamic select fields to Laravel Nova so options in one field can change based on another field's value. This makes dependent, cascading dropdowns such as state/city or category/subcategory easier to build without custom JavaScript. It is an admin/UI package for Nova resources, not a domain-critical application library.
- How do I install laravel-nova-field-dynamic-select in Laravel Nova?
- Adoption is typically a Composer install followed by field registration and configuration in a Nova resource. No application database migration is implied by the package. You need an existing Laravel application with Laravel Nova and a Nova license, and you should verify the package's Composer constraints against your stack.
- Which Laravel, PHP, and Nova versions does this Nova field support?
- The provided release notes do not announce specific Laravel, PHP, or Nova version constraints. Check the package composer.json against your current Nova major version, Laravel version, and PHP version before upgrading. Treat compatibility as something to verify rather than assume.
- How do I build cascading or dependent select fields in Laravel Nova?
- Configure the dynamic select field so its options are sourced based on another field's selected value. This supports dependent dropdowns such as state then city or category then subcategory without hand-written JavaScript. Test both create and update forms because dependent option loading can behave differently by form context.
- Do I need custom JavaScript for dependent dropdowns in Nova?
- The package is intended to make dependent, cascading dropdowns easier to build without custom JavaScript. You configure the Nova field and its dynamic option source instead of writing your own client-side logic. Keep option queries efficient, especially when the dependent data source is large.
- What changed in version 1.10.0 of laravel-nova-field-dynamic-select?
- Release 1.10.0 improves update-form behavior by sourcing resource fields from the specific resource instead of an empty generic resource, and it adds custom color support. The Laravel Mix 6 update is primarily build-tooling related and should not affect consumers using prebuilt assets. Existing edit-form configurations should be explicitly tested because the fix may expose assumptions in field setup.
- Does the Laravel Mix 6 update affect consumers of this package?
- Usually not if you consume prebuilt assets through Composer, because Mix is build tooling for maintainers or anyone rebuilding assets from source. If you fork the package or customize its assets, check your Node setup and build pipeline. Otherwise, focus validation on Nova create/update form behavior rather than asset compilation.
- How should I test a dynamic select field on Nova create and update forms?
- Smoke-test dependent option loading on both create and update forms, including changing the controlling field and saving the resource. Validate any custom color configuration and confirm field keys/names match your Nova resource definitions. Pin 1.10.0 in a staging branch before production, and roll back by pinning the prior package version if needed.
- Are there alternatives to this package for Laravel Nova dependent selects?
- Alternatives include built-in Nova field options, custom Nova fields, or writing your own JavaScript/Vue logic for dependent dropdowns. This package is a focused admin-layer dependency rather than a domain library. Evaluate maintainer support, Nova compatibility, and long-term maintenance before standardizing on it.
- How is royduin/laravel-nova-field-dynamic-select maintained and licensed?
- It is a community/open-source package with no vendor SLA, so support depends on maintainers and community involvement. The addition of a contributor is positive but does not materially remove support risk. Check the repository for license details and release cadence, and track package updates alongside Nova upgrades.