Deprecate the membership loader in favor of shared bundle classes

Created on 22 August 2023, over 1 year ago
Updated 6 September 2023, about 1 year ago

Essentially, the membership loader has bothered me for a while now. Even though it enables scenarios where you can swap out the service to load external memberships (like Active Directory), the key problem that arises is that our query access relies on said information to be stored in Drupal's database.

It feels like a broken promise to allow runtime membership info to come from an external source, but to rely on database info when checking query access. Therefore, we should take one step of abstraction back and make the system "know" that membership info always comes from the DB. In a later phase we could try and come up with a way for external systems like AD to populate the DB with the same necessary information.

Now that 📌 Allow shared bundle classes for group relationships using the same plugin Fixed has landed, we can already introduce a shared bundle class for memberships, but still keep the old membership loader and wrapper. This ensures full BC and in 4.0.0 we can then drop the membership loader and wrapper and start directly using the new shared bundle classes. But in the meantime, people who want to start using them already, can.

📌 Task
Status

Fixed

Version

3.1

Component

Code

Created by

🇧🇪Belgium kristiaanvandeneynde Antwerp, Belgium

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

Comments & Activities

Production build 0.71.5 2024