Releases: pktharindu/nova-permissions
Releases · pktharindu/nova-permissions
Fix display of permission groups
Make role resource group translatable
v2.1.4 Make Role resource group translatable
Role Resourse extend "App\Nova\Resource" instead of "Laravel\Nova\Resource"
v2.1.3 Update Role.php (#16)
Fix config table names
Fixed #12
Enable translations by default
made the group, display name, and description properties translatable.
Style changes
v2.1.0 fix styles
Major bug fix
Fixed the Role model which was replaced by AuthServiceProvider
Added the ability to configure table names
Database table names now can be configured using the config file.
// in config/nova-permissions.php
<?php
return [
// ...
/*
|--------------------------------------------------------------------------
| Database table names
|--------------------------------------------------------------------------
| When using the "HasRoles" trait from this package, we need to know which
| table should be used to retrieve your roles. We have chosen a basic
| default value but you may easily change it to any table you like.
*/
'table_names' => [
'roles' => 'roles',
'role_permission' => 'role_permission',
'role_user' => 'role_user',
],
// ...
];
Update packages and fix slug issue
Merge pull request #3 from tharindu-abans/master Update slug field
Added the ability to add custom role resource
If you want to use your own role resource, you can define it when you register the tool:
// in app/Providers/NovaServiceProvider.php
// ...
use App\Nova\Role;
public function tools()
{
return [
// ...
\Pktharindu\NovaPermissions\NovaPermissions::make()
->roleResource(Role::class),
];
}
Then extend the Pktharindu\NovaPermissions\Nova\Role
in your role resource:
// in app/Nova/Role.php
use Pktharindu\NovaPermissions\Nova\Role as RoleResource;
class Role extends RoleResource
{
// ...
}