- What is norman-huth/nova-perspectives used for?
- It is a Laravel Nova add-on for saving, managing, and switching between named perspectives on a Nova resource table. A perspective can define its own columns, filters, and sorting so the same resource can be presented in different ways without duplicating resource classes. Perspectives can be declared in code or created by users to keep a personalized Nova experience.
- Is norman-huth/nova-perspectives still maintained?
- No. The repository is archived and the package description explicitly says it is no longer maintained and points to the README for alternatives. The 2025-02-23 release date should not be read as active maintenance. There will be no security patches, compatibility fixes, or issue responses from upstream.
- How do I install nova-perspectives in a Laravel Nova application?
- Installation is a standard Composer require with Laravel package auto-discovery and a publishable config file. You then declare perspectives per Nova resource or allow users to manage their own. The mechanical effort is small, but you must first confirm that the package supports your Nova, Laravel, and PHP versions because the project is archived.
- Which Laravel and Nova versions does nova-perspectives support?
- The available context does not publish a clear, current compatibility matrix. Because the package is archived, you should inspect its composer.json constraints and run a short spike against your exact Nova major, Laravel version, and PHP version. Do not assume support for newer Nova or Laravel releases without verification.
- Can users create their own perspectives, or must they be defined in code?
- Both approaches are supported according to the package blurb. Developers can define perspectives in code for consistent shared views, and users can create their own perspectives for personal columns, filters, and sorting. That flexibility is the main value proposition, but it also means user-created perspectives need authorization review.
- Does nova-perspectives work with Laravel 11 and Nova 4 or 5?
- There is no confirmed support statement in the provided material. The package is archived, so compatibility with current Nova and Laravel majors is unverified and unlikely to be fixed upstream. Treat it as a spike candidate only, and test resource resolution, filtering, sorting, and authorization against your exact versions.
- What are maintained alternatives to nova-perspectives?
- The archive notice says to see the README for maintained alternatives, but the provided excerpt does not list them. You should check that README and also evaluate whether current Nova releases now ship equivalent native table-view or saved-view functionality. An in-house declarative config layer may be safer than adopting an archived package.
- Does a perspective hide data or only columns in the UI?
- Treat perspectives as a presentation-layer concern unless proven otherwise. Hiding a column in the UI does not necessarily constrain the underlying Eloquent query or API payload, which creates field-level leakage risk across roles. Audit the source to confirm whether any query or authorization constraints are applied before relying on it for access control.
- How should I test nova-perspectives in a Laravel application?
- Write feature tests in your own application because the package has no meaningful community test corpus or downstream users. Cover creating and switching perspectives, correct columns, filters, and sorting, and unauthorized users being unable to see restricted fields through Nova endpoints or APIs. Test the underlying resource responses, not only the browser UI.
- Is it safe to use an archived Composer package in production?
- It carries significant long-term risk: no security patches, no compatibility fixes, a single retired maintainer effort, and tight coupling to closed-source Nova internals that break between majors. You would become the de facto maintainer whether or not you plan for it. If you adopt it, pin the version, run a source audit, and budget to fork or reimplement rather than depend on upstream.