Closed callmejed closed 5 months ago
Hello there! Thanks for opening your first issue on this repo!
Just a heads-up: Here at Backpack we use Github Issues only for tracking bugs. Talk about new features is also acceptable. This helps a lot in keeping our focus on improving Backpack. If you issue is not a bug/feature, please help us out by closing the issue yourself and posting in the appropriate medium (see below). If you're not sure where it fits, it's ok, a community member will probably reply to help you with that.
Backpack communication mediums:
backpack-for-laravel
tag;Please keep in mind Backpack offers no official / paid support. Whatever help you receive here, on Gitter, Slack or Stackoverflow is thanks to our awesome awesome community members, who give up some of their time to help their peers. If you want to join our community, just start pitching in. We take pride in being a welcoming bunch.
Thank you!
-- Justin Case The Backpack Robot
Hi @callmejed!
I've read the upgrade guide and it seems there was a lot of changes/possible breaking changes. https://github.com/spatie/laravel-permission/blob/main/docs/upgrading.md#upgrading-from-v5-to-v6
We're probably work this out for the new backpack version.
We should be able to add support for spatie/laravel-permission
v6, it has nothing to do with backpack/crud
. We can do this:
backpack/permissionmanager
v7 will support spatie/laravel-permission
v3, v4, v5backpack/permissionmanager
v8 will support only spatie/laravel-permission
v6So yeah, I'd stay we should prioritize and do this, if people use the latest PermissionManager they can't add this Backpack add-on on top.
That would be fantastic <3
This one was fixed by @pxpm 3 weeks ago 🎉 https://github.com/Laravel-Backpack/PermissionManager/pull/356
I'm using Spatie ^6.1 so composer require fails since this package seems to require Spatie ^5.0