Permissions should declare their dependency on entity browser config entity

Created on 16 August 2023, 11 months ago

Problem/Motivation

Permissions provided by the module do not declare the dependency on the entity browser config entity itself.
This leads to situations where a role that has an entity browser permission assigned, is imported before the entity browser config entity itself.
Since the permission doesn't yet exist at that moment, a runtime exception will be thrown as all permissions must exist as per change record .

Steps to reproduce

  1. Create an entity browser;
  2. Assign the related permission to a role;
  3. Export the role and the entity browser (e.g. in a custom module);
  4. From a previous database dump, import the configuration (e.g. install the custom module of the previous step);

Proposed resolution

Permissions can declare their dependency on the config entity.

Remaining tasks

None.

User interface changes

None.

API changes

None.

Data model changes

None.

🐛 Bug report
Status

Needs review

Version

2.0

Component

Miscellaneous

Created by

🇮🇹Italy sardara

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.69.0 2024