- How do I install digital-creative/resource-navigation-link in a Laravel Nova application?
- Install it with Composer, then rely on Laravel package auto-discovery to register the service provider. Register the field on a Nova resource and configure the target as an internal resource class plus ID, a route, or an absolute URL. A realistic first spike is about half a day, with one to three days to standardize across resources. Confirm your PHP, Laravel, and Nova versions against composer.json before rollout.
- Which Laravel and Nova versions does resource-navigation-link support?
- The binding constraint is the Nova major version, so check composer.json for the supported Nova and Laravel matrix. The package is a Nova field, and Nova major versions have historically changed field APIs, so test on Nova 4 and Nova 5 if you run both. Do not infer support from the README alone; verify the field renders on index and detail views in your target version. PHP 8.x is the realistic baseline in the current ecosystem.
- How do I configure a resource-navigation-link field for an internal Nova resource?
- Add the field to the Nova resource's fields method and point it at the target resource class and record ID, or at the route you want to link to. Keep the configuration minimal at first: apply it to one low-traffic resource and verify the link appears on both index and detail views. Then standardize the pattern across related resources and review authorization behavior for each target. No schema migration or application service changes are required.
- Can resource-navigation-link create external URL links in Nova?
- Yes, the package is described as creating links to internal or external resources, so an absolute URL can be configured as the destination. Before using it for external destinations, confirm that it renders the anchor safely, including target=_blank and rel=noopener noreferrer if it opens a new tab. Also check display customization such as label, icon, and open-in-new-tab behavior. If those details are not documented, test them in a branch before standardizing.
- Does resource-navigation-link respect Nova authorization policies for internal resource links?
- This needs explicit verification, not assumption. Because the field generates links to internal Nova resources, it can expose resource identifiers or navigation paths if it does not honor authorizedToView or the target resource's policy checks. Test with a user who cannot view the target record and confirm whether the link is hidden or blocked. Treat authorization review as part of the adoption spike.
- Can I compute the resource-navigation-link target dynamically with a closure or callback?
- The key open question is whether the target can be computed dynamically, such as a route with parameters, or whether configuration is static only. Test a closure or callback in a branch against the package's actual field API before relying on it. If dynamic targets are not supported, keep the package for static links and use a small custom Nova field for computed destinations. This is a half-day spike item, not a blocker for the whole package.
- Does resource-navigation-link open external links safely in a new tab?
- The package does not automatically guarantee safe external-link behavior unless you verify it. Check that external destinations render with rel=noopener noreferrer when target=_blank is used, and confirm label and icon customization at the same time. If the field only produces a bare anchor, wrap or override the rendering in a fork. This is a low-cost review item with a real security surface.
- How does resource-navigation-link behave when the target record is missing or soft-deleted?
- A dangling link in an admin table becomes a support ticket, so test missing and soft-deleted targets explicitly. Confirm whether the field hides the link, renders a broken link, or throws an error on index and detail views. Soft deletes are the common case: the record still exists but should not be navigable. If behavior is unsafe, add a guard in the resource or vendor the field and own the check.
- Is digital-creative/resource-navigation-link actively maintained and tested?
- Treat maintenance as the primary risk: the package has very low community validation, zero dependents, and a single 2025-01-23 release from a Nova-specialist agency. That is a positive signal but not a commitment, and a dormant Nova field can break silently on a Nova major upgrade. Check for a test suite or CI and review the release history before adoption. The mitigation is cheap: vendor a few hundred lines of PHP and own it if the package stalls.
- What are the alternatives to resource-navigation-link and what is the exit cost?
- The realistic incumbents are an ad-hoc Text::make()->asHtml() anchor, a custom Nova Field subclass, or a Blade partial in a detail view. Migration is per-resource and incremental: swap the workaround for the package field, verify index and detail rendering, then delete the custom class. There is no data migration or downtime, and reversal is a one-line revert per resource. Exit cost is low because the field is presentation-layer only, so a fork of a few hundred lines is a viable hedge.