Merge branch '3.4.x' into 3.5.x

patchlevel · Sep 25, 2024 · 8b5e53c · 8b5e53c
2 parents 054253d + cfbe678
commit 8b5e53c
Show file tree

Hide file tree

Showing 3 changed files with 12 additions and 0 deletions.
diff --git a/docs/mkdocs.yml b/docs/mkdocs.yml
@@ -55,12 +55,14 @@ theme:
         name: Switch to light mode
 
 plugins:
+  - search:
   - mike:
       canonical_version: latest
   - privacy:
 
 markdown_extensions:
   - meta
+  - pymdownx.details
   - pymdownx.highlight:
       anchor_linenums: true
       extend_pygments_lang:

diff --git a/docs/pages/aggregate.md b/docs/pages/aggregate.md
@@ -360,6 +360,11 @@ final class Profile extends BasicAggregateRoot
 
 ## Child Aggregates
 
+??? example "Experimental"
+
+    This feature is still experimental and may change in the future.
+    Use it with caution.
+
 In some cases, it makes sense to split an aggregate into several smaller aggregates.
 This can be the case if the aggregate becomes too large or if the aggregate is used in different contexts.
 Child aggregates can be used for this purpose and work in the same way as the root aggregate.

diff --git a/docs/pages/store.md b/docs/pages/store.md
@@ -73,6 +73,11 @@ The table structure of the `DoctrineDbalStore` looks like this:
 
 ### StreamDoctrineDbalStore
 
+??? example "Experimental"
+
+    This feature is still experimental and may change in the future.
+    Use it with caution.
+
 We offer a new experimental store called `StreamDoctrineDbalStore`.
 This store is decoupled from the aggregate and can be used to store events from other sources.
 The difference to the `DoctrineDbalStore` is that the `StreamDoctrineDbalStore` merge the aggregate id