AE-157 Documentation for Strategy Resolver #3047
Conversation
gerner-spryker
added
new
|
The PR needs to be ready for merge, but only published when the related feature is released (will be contacted by a Product member). |
gerner-spryker
added
TW review needed
|
|
||
| --- | ||
|
|
||
| Spryker introduces context-based dependency resolution, such as plugin-stack, using a strategy resolver to handle complex workflows that stretch across multiple modules. This enhancement allows for defining multiple dependencies and selecting the appropriate one dynamically at runtime by the business logic. |
There was a problem hiding this comment.
What's an appropriate dependency?
There was a problem hiding this comment.
So, 1 plugin stack that uses strategy resolving, has multiple context. Each context is basically a separate individual plugin stack (with many plugins). When you seelct a context, you actually say which plugin stack to execute.
|
|
||
|
|
||
|
|
||
| # Context-Based Dependency Resolution in Spryker |
There was a problem hiding this comment.
Hey @gerner-spryker and @andriitserkovnyi
The whole below part looks like a duplicate of the above. Not a full copy-paste though but I don't get how is it different from the above
If you decide to merge it with the above - there's additional Q&A point that @profuel has added, don't forget it
|
the feature is already released https://github.com/spryker/kernel/releases/tag/3.77.0, so documentation should be also released |
PR Description
Spryker introduced Strategy Resolver concept for enabling context specific resolution for widely overarching workflows.
Tickets
Checklist