- Issue created by @pdureau
- 🇫🇷France pdureau Paris
Jean's notes:
Have dynamic config available to the instanciation of display builder `stateManager::create()` and to the user using the display builder.
So config should be permission based. Each config have a `use` permission.Implementation
For each instance associated with entity / page / views we should store a default config, when using `stateManager::create()` with fallback to default.
This value is stored as `entity_config_id` on the storage, it's a default value for this display builder.Display builder UX
Have a switch of display builder config when on a display builder, only available the one with current user permission and default to the default one set in state storage `entity_config_id`.
- 🇫🇷France mogtofu33
DB config, one global permission 'administer display builders' to create / edit Delete
For each DB config, one usage permission (as filter module):
Use the %name Display builder config - 🇫🇷France pdureau Paris
Filter module permissions, for information:
administer filters: title: 'Administer text formats and filters' description: 'Define how text is handled by combining filters into text formats.' restrict access: true permission_callbacks: - Drupal\filter\FilterPermissions::permissions