- What does mphpmaster/laravel-nova-blueprint-permission do?
- It is a Laravel Nova package that adds permission handling to Nova Blueprint resources. It is intended for admin-plane workflows where fields and generated resources need to be permission-aware. Treat it as an integration layer around Nova and your permission backend, not core domain authorization logic.
- How do I install laravel-nova-blueprint-permission in a Laravel Nova app?
- Install it with Composer using mphpmaster/laravel-nova-blueprint-permission, then follow the repository's publish and migration steps. Because the README excerpt is not available here, confirm the exact service provider, config publish, and migration commands before installing. Pin Laravel, Nova, PHP, and permission-backend constraints and test in a staging Nova app first.
- Which Laravel, PHP, and Nova versions does this package support?
- The provided assessment does not list exact Laravel, PHP, Nova, or permission-backend version constraints. Treat 3.0.0 as unverified until you review composer.json and the changelog. Build a compatibility matrix against your production versions and run CI before adopting it.
- Is version 3.0.0 a breaking change from 2.x?
- The assessment flags 3.0.0 as a major release with no published change summary in the provided notes, so breaking changes are possible. Do not assume a routine dependency bump. Review the 2.0.0-to-3.0.0 compare link, dependency constraints, migrations, and Nova resource or policy changes first.
- How does it integrate with Nova Blueprint resources?
- It is described as integrating permission handling with Nova Blueprint resources so you can define permission-aware fields and generate resource workflows from Blueprint definitions. Validate how your existing Blueprint definitions map to Nova resources and policies in a pilot. The package should be treated as an admin-plane integration, not a replacement for core authorization design.
- Does this package replace spatie/laravel-permission or a similar backend?
- The context says it integrates with permission handling but does not confirm whether it replaces or wraps a backend such as spatie/laravel-permission. Confirm from the repository whether it manages permissions only in the Nova UI or also affects application authorization paths. Test role resolution and cache behavior before relying on it.
- What migrations and config files does laravel-nova-blueprint-permission publish?
- The assessment notes migrations and config publishes as key review items but does not list their contents. Compare published files between versions and review schema, defaults, and permission seeds before running them in production. Keep a rollback plan for failed migrations or stale permission caches.
- How should I test Nova permission behavior before production?
- Pilot 3.0.0 in an isolated staging Nova app with representative roles and negative authorization tests. Seed roles and permissions, exercise admin workflows, and verify Nova route and resource registration. Also test permission cache clears and rollback procedures before canary rollout.
- What production risks should I consider with Nova permission packages?
- Permission packages are security-sensitive: incorrect role resolution or stale caches can cause privilege escalation or access outages. Validate caching, database indexes, and query patterns because permission checks may run on every request. Require break-glass and rollback procedures to avoid admin lockout.
- Is mphpmaster/laravel-nova-blueprint-permission actively maintained and what license does it use?
- The provided assessment says maintenance cadence and license are key questions and does not confirm either. Check the repository for license, release history, and recent activity before adopting it. Assign an internal owner for Composer constraints, Nova compatibility, and upgrade testing.