From 622e6c7f88e46e9f3f9a85408da092ff00b6c6a7 Mon Sep 17 00:00:00 2001 From: Karoly Gerner Date: Mon, 24 Feb 2025 12:45:51 +0100 Subject: [PATCH] Minor lock on factory changes --- docs/dg/dev/miscellaneous-guides/strategy-resolver.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/dg/dev/miscellaneous-guides/strategy-resolver.md b/docs/dg/dev/miscellaneous-guides/strategy-resolver.md index a34dc81997..259b076843 100644 --- a/docs/dg/dev/miscellaneous-guides/strategy-resolver.md +++ b/docs/dg/dev/miscellaneous-guides/strategy-resolver.md @@ -302,6 +302,9 @@ When multiple plugin-stacks contain a large number of plugins (10+), performance ## Frequently Asked Questions (FAQ) +### What kind of semantic versioning lock needs to be applied on the changes of the Factory when I define a new context? +Minor (as default). When a new context is introduced in a Project, it needs to be wired in the [Factory definition](#Configuring the Strategy Resolver in the Factory); any project change in a Spryker Factory requires a minor semantic versoning lock on that package. + ### Should I use this for all plugin-stacks? No, the strategy design pattern introduces complexity. Use it only when business logic requires it.