Nova Switch Laravel Package

Product Decisions This Supports

• Admin UX investment (small, reversible): ferdiunal/nova-switch is a Laravel Nova form field that renders boolean attributes (is_active, is_featured, published) as a toggle switch instead of a checkbox or select. Adoption is a UX polish decision for internal admin surfaces, not a product capability decision.
• Build vs. buy on Nova field components: Every custom Nova field means a Vue component plus maintenance across Nova major versions. Using a published field package trades a small dependency for that upkeep. This release does not change that calculus — it is a patch (v1.0.0 → v1.0.1) with no published API surface changes.
• Roadmap impact: none. This package should not appear on a roadmap as a deliverable or an enabler. It is tooling for the team operating the admin panel, and it should be scoped and budgeted as such (hours, not sprints).
• Risk posture: A 1.0.x package with a single maintainer and a changelog that is only a compare link is adoptable for internal tooling but should be version-pinned ("ferdiunal/nova-switch": "1.0.1") and treated as forkable, not as a strategic dependency.
• Release hygiene signal: v1.0.1 ships with no described changes. That is acceptable for a patch, but it means the release cannot be assessed on its merits. If this package is already in production, review the v1.0.0...v1.0.1 diff before upgrading rather than relying on the notes; if it is not yet adopted, this release is not a reason to adopt.

When to Consider This Package

Adopt when:

• You are already running Laravel Nova and have forms/index views where boolean flags are common and a checkbox reads poorly at a glance.
• Your team does not want to own a custom Vue field component, and a native Nova Boolean field is functionally sufficient but visually unsatisfying.
• The usage is internal admin tooling, where a bug means an awkward toggle rather than a customer-facing incident.
• You can pin the version and accept single-maintainer risk with a trivial fallback (swap back to Nova's native Boolean field — a one-line change per field).

Look elsewhere when:

• You are not on Laravel Nova. This package has no applicability outside it.
• You need richer behaviour than presentation: inline toggling in the index view, dependent/conditional fields, confirmation modals on destructive flips, audit logging of state changes, or coloured/semantic states. Nova's built-in field or a more actively governed field suite will serve better.
• You require a support SLA, security review guarantees, or multi-maintainer governance for anything in the admin path.
• Nova-version compatibility for your specific Nova release is unconfirmed. Verify this before committing, not after.

Non-negotiables before merge: confirm the Nova version constraint, read the actual diff for v1.0.1, and confirm the fallback path is genuinely one line.

How to Pitch It (Stakeholders)

To executives: This is a low-cost polish item for our internal admin panel — it makes on/off settings readable at a glance for the people operating the product. It has no customer-facing surface, no data model change, and no migration. Cost is measured in hours. The one caveat worth stating plainly is dependency hygiene: it is a small, single-maintainer open-source package, so we pin the exact version and can revert to Laravel Nova's built-in field with a one-line change per screen. That makes the downside bounded and the decision reversible.

To engineering: Thin wrapper around a Nova field — installs, registers, and renders a boolean as a switch. The v1.0.1 release is a patch with a changelog that only links to the v1.0.0…v1.0.1 compare view, so please review the diff rather than the notes before upgrading. No migrations, no config publishing expected, no API changes implied by the version bump. Pin the version, confirm the Nova constraint matches our install, and keep the native Boolean field as the documented fallback so this never becomes load-bearing. If we find ourselves wanting conditional logic, index-inline toggling, or change auditing, that is the signal to stop extending this and evaluate a better-governed alternative.