- What does sparclex/nova-creatable-belongs-to do?
- It provides a Laravel Nova BelongsTo field variant with an inline Create New option, letting operators create a related record directly from the parent form. It is an admin UX accelerator for Nova workflows, not a replacement for core domain logic. Keep business rules, approvals, and validation in application services and policies.
- How do I install sparclex/nova-creatable-belongs-to in Laravel Nova?
- Install it with Composer and use the package field in a Nova resource in place of a native BelongsTo field. Configure the relationship, searchable columns, and title attribute according to the repository documentation. Pin the package version and pilot it in a non-production environment before replacing production fields.
- Which Laravel, PHP, and Nova versions are supported by this package?
- The provided context does not list exact version constraints, so check composer.json and the repository README before adoption. Nova custom fields are sensitive to Nova major-version changes and frontend asset compatibility. Validate Laravel, PHP, and Nova constraints in a sandbox install against your application.
- Does inline creation respect Nova policies and authorization?
- Authorization is a key validation item and should not be assumed. Test inline creation with users who lack create permission and with different relationship contexts. If the field does not fully honor Nova resource policies, restrict it with Nova authorization, field visibility, or a fork.
- Does the field run Nova validation rules and model events when creating records?
- Verify this in a sandbox because inline creation must follow your Nova resource creation flow to honor validation, model events, defaults, and tenant scoping. Test validation failures and records that depend on model events. If the field bypasses expected workflows, use a dedicated resource action or custom field instead.
- Can I restrict who can create related records from the BelongsTo field?
- Use Nova policies, authorization checks, and field visibility to control when the inline create option is available. Test role-specific behavior for operators who can select records but should not create them. If the package lacks granular controls, implement restrictions in a custom field or fork.
- Does it support multi-tenancy, dependent fields, and duplicate prevention?
- These behaviors are not guaranteed by the package description and need validation in your application. Test tenant scoping, relationship search, dependent field behavior, and duplicate creation before rollout. Complex workflows should use a dedicated Nova resource or action that calls application services explicitly.
- Is sparclex/nova-creatable-belongs-to actively maintained and tested?
- It is a small community package with an MIT license and limited stars, so assume limited maintainership until you verify releases, issues, tests, and documentation. Assign an owner and monitor the repository. Composer and Nova upgrades should trigger regression testing of this field.
- Can I safely fork sparclex/nova-creatable-belongs-to if it becomes abandoned?
- Forking is likely feasible because it is a small Nova field package under the MIT license, but assess its frontend assets and Nova coupling first. Pin the current version and keep the native BelongsTo field as a rollback option. Document ownership and test the fork against future Nova releases.
- What are the alternatives to inline create in a Nova BelongsTo field?
- Alternatives include the native Nova BelongsTo field, a dedicated Nova resource or action, or a custom modal that calls application services. Use those approaches when creation requires approvals, multi-step workflows, tenancy rules, or strict deduplication. This package is best suited to simple admin-panel convenience where operators frequently create related records.