Download the PHP package marievych/roles without Composer
On this page you can find all versions of the php package marievych/roles. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download marievych/roles
More information about marievych/roles
Files in marievych/roles
Package roles
Short Description Powerful package for handling roles and permissions in Laravel 5.4
License MIT
Informations about the package roles
Roles And Permissions For Laravel 5.4
Powerful package for handling roles and permissions in Laravel 5.4
- Installation
- Composer
- Service Provider
- Config File And Migrations
- HasRoleAndPermission Trait And Contract
- Usage
- Creating Roles
- Attaching, Detaching and Syncing Roles
- Checking For Roles
- Inheritance
- Creating Permissions
- Attaching, Detaching and Syncing Permissions
- Checking For Permissions
- Entity Check
- Blade Extensions
- Middleware
- Config File
- More Information
- License
Installation
This package is very easy to set up. There are only couple of steps.
Composer
Pull this package in through Composer
Service Provider
Add the package to your application service providers in config/app.php file.
Config File And Migrations
Publish the package config file and migrations to your application. Run these commands inside your terminal.
php artisan vendor:publish --provider="Marievych\Roles\RolesServiceProvider" --tag=config
php artisan vendor:publish --provider="Marievych\Roles\RolesServiceProvider" --tag=migrations
And also run migrations.
php artisan migrate
This uses the default users table which is in Laravel. You should already have the migration file for the users table available and migrated.
HasRoleAndPermission Trait And Contract
Include HasRoleAndPermission trait and also implement HasRoleAndPermission contract inside your User model.
Usage
Creating Roles
Because of
Slugabletrait, if you make a mistake and for example leave a space in slug parameter, it'll be replaced with a dot automatically, because ofstr_slugfunction.
Attaching, Detaching and Syncing Roles
It's really simple. You fetch a user from database and call attachRole method. There is BelongsToMany relationship between User and Role model.
Checking For Roles
You can now check if the user has required role.
You can also do this:
And of course, there is a way to check for multiple roles:
Inheritance
If you don't want the inheritance feature in you application, simply ignore the
parent_idparameter when you're creating roles.
Roles that are assigned a parent_id of another role are automatically inherited when a user is assigned or inherits the parent role.
Here is an example:
You have 5 administrative groups. Admins, Store Admins, Store Inventory Managers, Blog Admins, and Blog Writers.
| Role | Parent |
|---|---|
| Admins | |
| Store Admins | Admins |
| Store Inventory Managers | Store Admins |
| Blog Admins | Admins |
| Blog Writers | Blog Admins |
The Admins Role is the parent of both Store Admins Role as well as Blog Admins Role.
While the Store Admins Role is the parent to Store Inventory Managers Role.
And the Blog Admins Role is the parent to Blog Writers.
This enables the Admins Role to inherit both Store Inventory Managers Role and Blog Writers Role.
But the Store Admins Role only inherits the Store Inventory Managers Role,
And the Blog Admins Role only inherits the Blog Writers Role.
Another Example:
| id | slug | parent_id |
|---|---|---|
| 1 | admin | NULL |
| 2 | admin.user | 1 |
| 3 | admin.blog | 1 |
| 4 | blog.writer | 3 |
| 5 | development | NULL |
Here,
admin inherits admin.user, admin.blog, and blog.writer.
While admin.user doesn't inherit anything, and admin.blog inherits blog.writer.
Nothing inherits development and, development doesn't inherit anything.
Creating Permissions
It's very simple thanks to Permission model.
Attaching, Detaching and Syncing Permissions
You can attach permissions to a role or directly to a specific user (and of course detach them as well).
Checking For Permissions
You can check for multiple permissions the same way as roles. You can make use of additional methods like hasOnePermission or hasAllPermissions.
Entity Check
Let's say you have an article and you want to edit it. This article belongs to a user (there is a column user_id in articles table).
This condition checks if the current user is the owner of article. If not, it will be looking inside user permissions for a row we created before.
Blade Extensions
There are four Blade extensions. Basically, it is replacement for classic if statements.
Middleware
This package comes with VerifyRoleand VerifyPermission middleware. You must add them inside your app/Http/Kernel.php file.
Now you can easily protect your routes.
It throws \Marievych\Roles\Exceptions\RoleDeniedException, \Marievych\Roles\Exceptions\PermissionDeniedException exceptions if it goes wrong.
You can catch these exceptions inside app/Exceptions/Handler.php file and do whatever you want.
Config File
You can change connection for models, slug separator, models path and there is also a handy pretend feature. Have a look at config file for more information.
More Information
For more information, please have a look at HasRoleAndPermission contract.
License
This package is free software distributed under the terms of the MIT license.