Laravel-permission: Do you support permissions and roles to add alias features?

[swat199538]

I think this is useful features.

[drbyte]

Can you explain in more detail?

[swat199538]

Because of my background to the management of these rights and role, but I was using Chinese, I can not directly show these permissions and role values, the user will feel strange, so I had to create a new table to do these permissions and roles of the Chinese show that if you can support the alias native so tell me about the demand will be easier to use.

[ankurk91]

I have faced similar issue in past.
Right now both role and permission tables have a single database column name that is being used as unique slug.
For example the permission name is create_post and i want to show Ability to create posts on UI.
Same goes with role.
I would like to have a new column to hold display_name that we can allow our customer to change without the need of changing the slug (name).

[AlexVanderbist]

I can see how this is a problem. However you can easily update the permissions table migration to include a display_name column. The Permission class is an eloquent model so you can set that display name property like this:

Permission::create(['name' => 'articles.edit', 'display_name' => "Edit articles"]);

I'm not sure if we want to include this in the actual package as it's something you can easily do yourself. Maybe we can include a section in the readme about custom properties? (mentioning #479 so I don't forget)

[bjuppa]

I'm not sure this solves your problem, but to display permission and role names in a more user friendly way in the interface, perhaps you could pass names through the Laravel translation functions, like

__($role->name)

and define the display string you want in the language files?

https://laravel.com/docs/5.5/localization#using-translation-strings-as-keys

[akongnwi02]

@bjuppa This makes more sense to me