Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove all adapters from plugin manager #55

Merged

Conversation

boesing
Copy link
Member

@boesing boesing commented Nov 19, 2020

Q A
BC Break yes

Description

Adapters have to register themselves to the AdapterPluginManager.
This can be done by using a DelegatorFactory from within the adapter repository. This way, 3rd-party adapters can inject themselves into the laminas-cache ecosystem.

@boesing boesing added this to the 3.0.0 milestone Nov 19, 2020
@boesing boesing mentioned this pull request Jan 1, 2021
@boesing boesing marked this pull request as ready for review February 8, 2021 18:32
@boesing boesing force-pushed the qa/remove-adapters-from-pluginmanager branch from add1ed8 to 2480bfb Compare July 31, 2021 12:21
@boesing boesing changed the title qa: remove all adapters from plugin manager Remove all adapters from plugin manager Jul 31, 2021
@boesing boesing force-pushed the qa/remove-adapters-from-pluginmanager branch from 2480bfb to 501ab1a Compare July 31, 2021 12:22
Adapters have to register themselves to the `AdapterPluginManager`.
This can be done by using a `DelegatorFactory` from within the adapter repository. This way, 3rd-party adapters can inject themselves into the `laminas-cache` ecosystem.

Signed-off-by: Maximilian Bösing <[email protected]>
@boesing boesing force-pushed the qa/remove-adapters-from-pluginmanager branch from 501ab1a to 0d1d9f9 Compare July 31, 2021 12:23
@boesing boesing merged commit 8bdb0c2 into laminas:3.0.x Jul 31, 2021
@boesing boesing deleted the qa/remove-adapters-from-pluginmanager branch February 14, 2022 15:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants