Weave Code
Nova Inline Text Field Laravel Package
outl1ne/nova-inline-text-field
Nova Inline Text Field lets you edit text values directly from the Laravel Nova resource index without opening a detail page. Click, type, save—fast inline updates for a smoother admin workflow.
A Laravel Nova inline text field.
Frequently asked questions about Nova Inline Text Field
- How do I install outl1ne/nova-inline-text-field?
- Install it with Composer using composer require outl1ne/nova-inline-text-field:^3.0.1. Nova auto-discovers the field, so there is no service provider wiring, config publishing, or data migration. Then use InlineText::make(...) on a Nova resource like any other field. Budget about a half-day to verify compatibility and exercise the inline edit flow end to end.
- Does outl1ne/nova-inline-text-field support Laravel Nova 4 and Nova 5?
- The package is intended for Laravel Nova v4 and v5, and adoption is strictly conditional on already running a supported Nova major. Confirm the exact Nova and PHP constraints in the package composer.json before installing. The 3.0.1 patch specifically fixes an InlineText method-signature incompatibility with its parent class, which is a typical Nova contract change. If your admin surface is not Nova or is migrating off Nova, this package is out of scope.
- Why should I pin ^3.0.1 and avoid version 3.0.0?
- Version 3.0.1 is a one-commit patch that fixes an InlineText method-signature incompatibility with its parent class. That means 3.0.0 shipped broken and can produce a fatal error at resource registration. Pin ^3.0.1 and never install 3.0.0. Exact-version pinning in composer.lock is the control.
- How do I use InlineText in a Laravel Nova resource?
- Register it like any Nova field on the resource, for example InlineText::make('Name'), and it turns that string column into an in-place editable input in the index or detail table. Click, type, and save writes through Nova's standard update endpoint without opening a detail page. Keep a documented fallback to Text::make(...) in case the field breaks.
- Do inline saves enforce Nova policies and field validation rules?
- Inline saves go through Nova's standard update endpoint, so authorization should follow the resource update policy, but the assessment explicitly calls for proving that path rather than assuming it. Verify that view-only users cannot write and that ->rules(...) on the field still apply to inline edits. Exercise the authorization and validation paths end to end before rollout. If they do not hold, treat it as a blocker.
- Do inline edits fire Eloquent observers and update updated_at?
- Because the field writes through Nova's standard update endpoint, edits should follow the normal Eloquent update path, including observers, updated_at, and audit packages. The technical assessment flags this as a question to verify rather than a proven behavior. Test it in staging with your observers and audit logging enabled. If your workflow depends on those events, confirm before adopting.
- What is the blast radius if outl1ne/nova-inline-text-field breaks?
- The blast radius is one field type on one admin surface, and it degrades gracefully because editors can fall back to the normal edit form. However, a parent-class signature mismatch can surface as a fatal error at resource registration, taking down the entire index or detail view for that resource. Pin the exact version in composer.lock and keep the Text::make(...) fallback written down and owned. Removal is a Composer revert plus an asset rebuild.
- What are alternatives to using this package for inline editing in Nova?
- The built-in Text field plus the standard edit form is the primary alternative and the fallback. Nova also has other community inline-edit packages, but none are assessed here. For this scope, using InlineText only on low-risk string columns and keeping Text::make(...) available gives most of the convenience with less exposure. If your admin surface is moving off Nova, do not add this dependency.
- How do I remove outl1ne/nova-inline-text-field later?
- Revert the resource fields from InlineText::make(...) back to Text::make(...), remove the Composer package, and rebuild Nova assets. There is no schema change, no published config, and no data migration, so the reversal path is short. This low-ceremony removal is why adoption is a small, reversible decision.
- Is outl1ne/nova-inline-text-field actively maintained and tested?
- It is effectively single-maintainer with around 23 stars, zero dependents, and no evidence of an automated test suite, so assume manual verification only. The 3.0.1 patch shows the maintainer tracks the Nova parent class, but 3.0.0 shipping broken is also a release-hygiene signal. Check the maintainer's release cadence and issue-response record, and decide what abandonment would cost you. At this blast radius it can be acceptable if the fallback is documented and owned.
Weaver
How can I help you explore Laravel packages today?