Weave Code
Nova Dependency Container Laravel Package
outl1ne/nova-dependency-container
Outl1ne Nova Dependency Container adds a container field to Laravel Nova that shows or hides nested fields based on another field's value, so you can build conditional, dynamic forms and admin panels without writing custom JavaScript, Vue or complex field logic.
A Laravel Nova field container allowing to depend on other fields values
Frequently asked questions about Nova Dependency Container
- How do I install outl1ne/nova-dependency-container?
- Install it with Composer using composer require outl1ne/nova-dependency-container. The package is a Laravel Nova package, so Laravel auto-discovers its service provider; after installing, clear cached config and Nova assets if needed. Check the README for any version-specific setup steps before using it in a project.
- What Laravel Nova versions does outl1ne/nova-dependency-container support?
- Supported Nova versions are defined in the package composer.json and release notes, so check those constraints before installing. Nova major upgrades can change field APIs, so test the package after upgrading Nova. If you need an older Nova version, use the matching package release rather than forcing Composer constraints.
- How do I show or hide Nova fields based on another field's value?
- Wrap the fields that should be conditional inside a dependency container and define the controlling field and the value that should trigger visibility. When the controlling field changes, Nova updates the container without custom JavaScript or Vue code. This keeps conditional form logic declarative and easier to maintain in admin panels.
- Can a dependency container depend on multiple fields or multiple values?
- The package is built around conditional containers tied to field values; the exact support for multiple values, operators, and combined dependencies depends on the current release. Check the README for the supported dependency API before designing complex forms. For advanced logic, you can often combine or nest containers where supported, but keep the rules simple for maintainers.
- Does Nova Dependency Container require custom JavaScript or Vue components?
- No, the package provides a Nova field container that handles visibility through Nova's field system. You define dependencies in PHP when building the form, so you do not need to write custom JavaScript or Vue code. That makes it a good fit for teams that want conditional forms without maintaining frontend assets.
- Can I nest dependency containers inside each other?
- Nested containers are commonly used to build layered conditional forms, but you should confirm nesting behavior for your exact package and Nova versions. Each container evaluates its own dependency, so keep the hierarchy shallow where possible to avoid confusing admin UX. Test the form interactions after Nova upgrades.
- Are hidden fields still submitted or validated?
- The container primarily controls UI visibility, so you should not assume hidden fields are automatically excluded from every validation or request flow. Validate conditional data explicitly in your Nova resource rules and test the request payload for your use case. This is especially important for required fields and business-critical admin forms.
- How do I test forms built with Nova Dependency Container?
- Test the underlying Nova resource validation and field logic, and add browser-level checks for the visibility behavior if conditional forms are critical. In Laravel tests, assert that valid and invalid payloads behave correctly regardless of what the UI shows. After upgrading Nova or the package, manually verify that containers still react to field changes.
- What are alternatives to outl1ne/nova-dependency-container?
- Alternatives include Nova's native field dependency options where they fit, custom Nova fields, or other conditional-field packages. A container package is useful when you want to group many fields behind one condition without duplicating dependency logic. Compare maintenance status, Nova version support, and whether you need nested or multi-field conditions.
- Is outl1ne/nova-dependency-container maintained and safe for production?
- Check the GitHub repository and Packagist releases for recent activity, open issues, and Nova version compatibility before adopting it. Pin a tested version in composer.json and include it in your Nova upgrade checklist. For production admin panels, verify the package behavior in staging with your actual field combinations.
Weaver
How can I help you explore Laravel packages today?