Weave Code
Novafieldcheckboxes Laravel Package
silvanite/novafieldcheckboxes
A Laravel Nova field package that adds checkbox inputs to your resources: a single boolean checkbox or a group of options stored as JSON, with labels, defaults and validation configured in PHP.
A Laravel Nova field to display a number of multi-select options using checkboxes.
Frequently asked questions about Novafieldcheckboxes
- How do I install silvanite/novafieldcheckboxes in a Laravel Nova application?
- Install it with Composer using silvanite/novafieldcheckboxes, then add the Silvanite\NovaFieldCheckboxes\Checkboxes field to a Nova resource's fields() method. You also need to confirm the underlying database column type and add an array or JSON cast on the model. The package is a Nova form field, so it does not require application routing or service configuration beyond Nova's normal field registration.
- Which Laravel, PHP, and Nova versions does this checkbox field support?
- The package's composer.json is the source of truth for its Laravel, PHP, and Nova constraints, so check it before adopting. This is the most common failure point for small Nova field packages because Nova's field API and frontend conventions change across majors. Confirm the declared Nova major matches your release rather than assuming compatibility from the README alone.
- How are selected checkbox values stored in the database?
- The field persists the selected option keys as an array into a single column, typically JSON or a text column with a cast. You must add the matching array or JSON cast on the Eloquent model. A missing or mismatched cast can produce an Array to string conversion error or a silently stringified value that breaks on read. Verify the stored shape survives the cast, the Nova detail view, and the index display.
- Can this field render a single boolean checkbox as well as a group of options?
- Yes. The package supports a single boolean checkbox or a group of options stored as JSON. Labels, defaults, and validation are configured in PHP through the field class. Use the boolean mode when you need one on/off flag and the grouped mode when you need multiple selections from a known option set.
- How do I validate that at least one checkbox option is selected?
- Use standard Laravel array-level validation such as required, array, and min:1 when at least one selection is mandatory. For allowed values, use Rule::in against the same option source the field uses, for example array_keys(config('options.x')). Sharing one option source between the field and the validation rules prevents drift between what is displayed and what is accepted.
- Why does my checkbox field show unreadable JSON in the Nova index table?
- A raw JSON array is unreadable in the Nova index, and the package does not automatically format it for you. Use displayUsing() on the field to render a readable label or joined option names. Consider hideFromIndex when the raw value adds no value to the index listing. Test the display alongside Nova search and filters for your version.
- Is this package a good alternative to Nova's native BooleanGroup field?
- Nova's native BooleanGroup also stores multiple selections as JSON and may cover the same requirement at zero dependency cost. Evaluate whether the native field or a refined multi-select already satisfies your use case before adding this package. If the native field is sufficient, the correct decision is to add no dependency at all.
- Do I need to compile the Vue assets, or are they prebuilt?
- The overview does not state whether the Vue assets are prebuilt, so verify this before adopting. Check the package's distributed files and release contents, and confirm compatibility with your Nova major's asset pipeline. If assets must be compiled, account for that effort in your adoption estimate.
- Is silvanite/novafieldcheckboxes actively maintained and safe for production?
- The adoption signal is weak, with roughly 67 stars and zero known dependents, so there is little community pressure to track Nova releases. Check the last commit date, open issues, and stale pull requests before committing, ideally confirming activity within roughly the last 12 months. The blast radius is confined to Nova admin resources, which caps the downside, but you should still name an individual who owns the fork if upstream stalls.
- What should I watch out for with JSON round-tripping and all-unchecked submissions?
- Decide explicitly whether an all-unchecked form should submit an empty array or null, and implement that normalization, with a mutator being the cleanest home. Verify the value round-trips correctly through the model cast, the Nova detail view, and the index. If you need to query selections, use whereJsonContains against the stored JSON array.
Weaver
How can I help you explore Laravel packages today?