If you have two modules that declare the same permission name, the manage permissions form only shows one.
e.g.
opt-in or out of tracking:
title: 'Opt-in or out of tracking'
description: 'Allow users to decide if tracking code will be added to pages or not.'
use PHP for tracking visibility:
title: 'Use PHP for tracking visibility'
description: 'Enter PHP code in the field for tracking visibility settings.'
restrict access: true
Namespace permissions to the provider they came from.
e.g. `node:create page content`
Add support
Add test coverage
Write BC layer (e.g. calls to add a permission should just work if the provider isn't added, but log a deprecation error).
Update path for roles
None
None.
Maybe
Active
11.0 🔥
Last updated
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Is that all you need to enforce namespacing and preventing collisions?
Don't we want to enforce module name prefix when we are loading permissions from the file
Also any reason whey we can't auto prefix the module name to the permission name when we load permissions from the file?