Weave Code
Resource Index Link Laravel Package
causelabs/resource-index-link
Adds clickable links to Laravel Nova resource index rows, letting you point each row at a related resource, custom URL, or action instead of the default detail page. Lightweight and easy to configure.
A Laravel Nova extension that creates a text input that displays as a link to a resource when indexed.
Frequently asked questions about Resource Index Link
- What is causelabs/resource-index-link used for in Laravel Nova?
- It provides a Nova text input field that renders as a clickable link in resource index rows. You can point each row to a related resource, custom URL, or action instead of the default detail page. It is lightweight and configurable.
- How do I install causelabs/resource-index-link in a Laravel Nova app?
- Install it with Composer using composer require causelabs/resource-index-link. Then add the field to the fields method of your Nova resource. Consult the README for any required configuration or publishing steps, and confirm compatibility with your Laravel and Nova versions.
- Does causelabs/resource-index-link support UUID, ULID, slug, or custom resource keys?
- The v1.0.5 release adds support for resource keys other than the standard id. That makes it viable for resources using UUIDs, ULIDs, slugs, or other stable identifiers. Confirm which layers honor the custom key, such as route model binding and relationships, before standardizing.
- Can I link a Nova index row to a custom URL or action instead of the resource detail page?
- Yes, the package is described as letting you point each row at a related resource, custom URL, or action instead of the default detail page. That lets you tailor index navigation for workflows. Check the field API for the exact URL or action configuration.
- Is causelabs/resource-index-link compatible with my Laravel and Nova versions?
- The package is a Laravel Nova extension, so compatibility depends on your Nova version and Laravel and PHP stack. There is no explicit version matrix in the provided overview, so test in a feature branch. Verify service-provider auto-discovery, route caching, and field rendering.
- Does upgrading to causelabs/resource-index-link v1.0.5 introduce breaking changes?
- The release is described as additive, focused on resource-key resolution rather than a broad architectural shift. No breaking change is indicated, but the release note is sparse. Run regression tests for existing id-based resources and canary one custom-key endpoint before rollout.
- How does causelabs/resource-index-link handle route model binding and nested resources with custom keys?
- The overview says v1.0.5 adds support for resource keys other than id, which aligns with Laravel route model binding conventions. However, the release note is sparse, so confirm how nested routes, relationship bindings, and serialization honor the custom key. Add targeted tests for UUID, ULID, or slug routes.
- What should I watch out for in production when using custom resource keys with this package?
- Ensure custom keys are unique and properly indexed in the database to avoid ambiguous lookups. Verify authorization scoping still applies when resolving by a non-id key. Watch for route-cache issues after configuration changes and keep id behavior unchanged on existing endpoints.
- How should I test causelabs/resource-index-link in a Laravel app?
- Add regression tests for existing id-based Nova index links, then add targeted tests for UUID, ULID, slug, or custom-key routes. Verify route model binding, authorization scoping, nested resources, and route caching. Stage and canary one endpoint before broader rollout.
- Is causelabs/resource-index-link actively maintained, and are there alternatives?
- Maintenance impact is low if the package remains actively maintained and custom-key behavior is documented. The overview does not list release cadence or alternatives, so review the repository and issue tracker. Alternatives may include Nova's built-in fields or custom field implementations, depending on your linking needs.
Weaver
How can I help you explore Laravel packages today?