[create-pull-request] automated change

Author: shopwareBot

SUMMARY.md

@@ -452,6 +452,7 @@
     * [Tax providers](resources/references/adr/2022-04-28-tax-providers.md)
     * [Remove static analysis with psalm](resources/references/adr/2022-05-12-remove-static-analysis-with-psalm.md)
     * [Rule condition field abstraction](resources/references/adr/2022-05-23-rule-condition-field-abstraction.md)
+    * [Integrate app into flow event](resources/references/adr/2022-06-17-integrate-app-into-flow-event.md)
     * [Add typescript support for storefront js](resources/references/adr/2022-06-24-add-typescript-support-for-storefront-js.md)
     * [Providing the admin extension sdk](resources/references/adr/2022-06-27-providing-the-admin-extension-sdk.md)
     * [Blog concept](resources/references/adr/2022-07-19-blog-concept.md)
@@ -478,7 +479,30 @@
     * [Admin text editor evaluation](resources/references/adr/2023-03-27-admin-text-editor-evaluation.md)
     * [Mocking repositories](resources/references/adr/2023-04-01-mocking-repositories.md)
     * [Disable css autoprefixer](resources/references/adr/2023-04-03-disable-css-autoprefixer.md)
+    * [New language inheritance mechanism for opensearch](resources/references/adr/2023-04-11-new-language-inheritance-mechanism-for-opensearch.md)
     * [Jest test files should be javascript only](resources/references/adr/2023-04-14-jest-test-files-should-be-javascript-only.md)
+    * [Optimise cart cleanup](resources/references/adr/2023-05-09-optimise-cart-cleanup.md)
+    * [Experimental features](resources/references/adr/2023-05-10-experimental-features.md)
+    * [Stock API](resources/references/adr/2023-05-15-stock-api.md)
+    * [Php enums](resources/references/adr/2023-05-16-php-enums.md)
+    * [Symfony dependency management](resources/references/adr/2023-05-16-symfony-dependency-management.md)
+    * [Switch to uuidv7](resources/references/adr/2023-05-22-switch-to-uuidv7.md)
+    * [Exception log levels](resources/references/adr/2023-05-25-exception-log-levels.md)
+    * [Store API to app server](resources/references/adr/2023-06-27-store-api-to-app-server.md)
+    * [Default handle for non specified salutations](resources/references/adr/2023-06-28-default-handle-for-non-specified-salutations.md)
+    * [Flow builder preview](resources/references/adr/2023-07-13-flow-builder-preview.md)
+    * [Collecting entity data](resources/references/adr/2023-08-03-collecting-entity-data.md)
+    * [Media path](resources/references/adr/2023-08-17-media-path.md)
+    * [Post updater](resources/references/adr/2023-08-27-post-updater.md)
+    * [Feature property for experimental anotation](resources/references/adr/2023-09-06-feature-property-for-experimental-anotation.md)
+    * [Catalog import API](resources/references/adr/2023-09-22-catalog-import-api.md)
+    * [Add unique identifiers for checkout methods](resources/references/adr/2023-10-17-add-unique-identifiers-for-checkout-methods.md)
+    * [Bootstrap css utils](resources/references/adr/2023-10-19-bootstrap-css-utils.md)
+    * [Toggle feature flag on demand](resources/references/adr/2023-11-29-toggle-feature-flag-on-demand.md)
+    * [Acceptance test suite](resources/references/adr/2023-12-12-acceptance-test-suite.md)
+    * [Transactional flow actions](resources/references/adr/2024-02-11-transactional-flow-actions.md)
+    * [Disable vue compat mode per component level](resources/references/adr/2024-03-11-disable-vue-compat-mode-per-component-level.md)
+    * [Implementation of meteor component library](resources/references/adr/2024-03-21-implementation-of-meteor-component-library.md)
     * [YYYY MM DD template](resources/references/adr/YYYY-MM-DD-template.md)
 
   * [App Reference](resources/references/app-reference/README.md)

resources/references/adr/2020-06-25-implement-architecture-decision-records.md

@@ -3,14 +3,7 @@ title: Implement architecture decision records
 date: 2020-06-25
 area: core
 tags: [adr, workflow]
---- 
-
-# Implement architecture decision records
-
-{% hint style="info" %}
-This document represents an architecture decision record (ADR) and has been mirrored from the ADR section in our Shopware 6 repository.
-You can find the original version [here](https://github.com/shopware/platform/blob/trunk/adr/2020-06-25-implement-architecture-decision-records.md)
-{% endhint %}
+---
 
 ## Context
 We should document architecture and technical decisions for the shopware platform. The documentation should be easy to understand and easy to follow. The workflow for new decisions should add to our existing workflows and should not block the whole development process. One solution could be the form of architecture decision records (ADR) as described in the following articles:
@@ -53,7 +46,7 @@ The ADRs are markdown files inside the platform repository, located in the "adr"
    *  One developer must be a member of the core development team
    *  One developer must be a member of a team, other than the team of the creator
 * One product owner or higher role has to approve an ADR
-** This part of the decision is superseded by [2021-11-05 - Adjust ADR approval rules for the new org structure](2021-11-05-adjust-ADR-approval-rules.md), but the rest of this ADR is untouched.**
+** This part of the decision is superseded by [2021-11-05 - Adjust ADR approval rules for the new org structure](2021-11-05-adjust-adr-approval-rules.md), but the rest of this ADR is untouched.**
 
 **Should counter decisions also be documented?**   
 Not specific, but if there is more than one possible solution, all options should be outlined.
@@ -73,4 +66,3 @@ The status of an ADR is symbolized by the directory. All ADR located in the main
 
 **Can an ADR be changed?**  
 When an ADR is accepted and merged in to the code, it can no longer be changed. If a decision is outdated or has to be changed, the ADR has to be superseded by a new ADR. Superseded ADRs have to be moved to the `/adr/_superseded` directory.
-

resources/references/adr/2020-07-02-control-clone-behavior.md

@@ -3,14 +3,7 @@ title: Get control of association clone behavior as developer
 date: 2020-07-02
 area: core
 tags: [repository, entity, clone, flag, association]
---- 
-
-# Get control of association clone behavior as developer
-
-{% hint style="info" %}
-This document represents an architecture decision record (ADR) and has been mirrored from the ADR section in our Shopware 6 repository.
-You can find the original version [here](https://github.com/shopware/platform/blob/trunk/adr/2020-07-02-control-clone-behavior.md)
-{% endhint %}
+---
 
 ## Context
 The developer should be able to define, if an association has to be considered or skipped during the cloning of an entity.

resources/references/adr/2020-07-02-implement-sales-channel-context-token-requirement.md

@@ -3,14 +3,7 @@ title: Implement sales channel context token requirement for store-api and sales
 date: 2020-07-02
 area: core
 tags: [context, token, sales-channel, store-api, sales-channel-api, api]
---- 
-
-# Implement sales channel context token requirement for store-api and sales-channel-api
-
-{% hint style="info" %}
-This document represents an architecture decision record (ADR) and has been mirrored from the ADR section in our Shopware 6 repository.
-You can find the original version [here](https://github.com/shopware/platform/blob/trunk/adr/2020-07-02-implement-sales-channel-context-token-requirement.md)
-{% endhint %}
+---
 
 ## Context
 Some routes for the sales-channel-api and the store-api depend on a sales-channel-context-token to identify the correct context.

resources/references/adr/2020-08-03-implement-new-changelog.md

@@ -3,14 +3,7 @@ title: Implement new changelog
 date: 2020-08-03
 area: core
 tags: [changelog]
---- 
-
-# Implement new changelog
-
-{% hint style="info" %}
-This document represents an architecture decision record (ADR) and has been mirrored from the ADR section in our Shopware 6 repository.
-You can find the original version [here](https://github.com/shopware/platform/blob/trunk/adr/2020-08-03-implement-new-changelog.md)
-{% endhint %}
+---
 
 ## Context
 The current workflow for writing technical changelog is not very suited for a trunk based development and branching process. There are some major issues with the current workflow of using one file with a fixed version number:
@@ -118,4 +111,3 @@ If you just want to get the changes of a specific version or even just a special
 `bin/console changelog:change [<version>] [options]`
 
 Use the `--help` flag of the command to see all possible options.
-

resources/references/adr/2020-08-10-feature-flag-system.md

@@ -5,13 +5,6 @@ area: core
 tags: [feature-flag, workflow]
 ---
 
-# Feature flag system
-
-{% hint style="info" %}
-This document represents an architecture decision record (ADR) and has been mirrored from the ADR section in our Shopware 6 repository.
-You can find the original version [here](https://github.com/shopware/platform/blob/trunk/adr/2020-08-10-feature-flag-system.md)
-{% endhint %}
-
 ## Superseded by [Feature flags for major versions](2022-01-20-feature-flags-for-major-versions.md)
 
 ## Context

resources/references/adr/2020-08-12-document-template-refactoring.md

@@ -3,14 +3,7 @@ title: Document template refactoring
 date: 2020-08-12
 area: customer-order
 tags: [document, template, twig]
---- 
-
-# Document template refactoring
-
-{% hint style="info" %}
-This document represents an architecture decision record (ADR) and has been mirrored from the ADR section in our Shopware 6 repository.
-You can find the original version [here](https://github.com/shopware/platform/blob/trunk/adr/2020-08-12-document-template-refactoring.md)
-{% endhint %}
+---
 
 ## Context
 Our document templates did not support nested line items. To make this possible, we had to split the document templates into smaller templates.

resources/references/adr/2020-08-12-implement-app-system-inside-platform.md

@@ -3,14 +3,7 @@ title: Implement app system inside platform
 date: 2020-08-12
 area: core
 tags: [app, cloud]
---- 
-
-# Implement app system inside platform
-
-{% hint style="info" %}
-This document represents an architecture decision record (ADR) and has been mirrored from the ADR section in our Shopware 6 repository.
-You can find the original version [here](https://github.com/shopware/platform/blob/trunk/adr/2020-08-12-implement-app-system-inside-platform.md)
-{% endhint %}
+---
 
 ## Context
 
@@ -56,7 +49,7 @@ Additionally, the storefront theme files (JS and CSS) only need to be accessed d
 
 * [Custom Fields](https://docs.shopware.com/en/shopware-platform-dev-en/app-system-guide/app-base-guide?category=shopware-platform-dev-en/app-system-guide#custom-fields): An app can register it's own custom fields sets, that are displayed along the other custom fields inside the administration.
 
-* [Storefront Customizations](https://docs.shopware.com/en/shopware-platform-dev-en/app-system-guide/app-examples-and-tutorials/create-own-theme?category=shopware-platform-dev-en/app-system-guide/app-examples-and-tutorials): An app should be able to customize the storefront in the same way a plugin does. This includes the theme system, custom twig templates and custom JS and CSS.
+* [Storefront Customizations](https://developer.shopware.com/docs/guides/plugins/apps/storefront/): An app should be able to customize the storefront in the same way a plugin does. This includes the theme system, custom twig templates and custom JS and CSS.
 In regard to the theme system apps are treated the same way as plugins are, especially regarding the theme inheritance. Apps can be explicitly set in the inheritance chain via `@TechnicalAppName`, if they are not referenced directly they are part of the fallback `@Plugins` namespace.
 
 Extension points may be added as new features of the app system, but we have to make sure that it does not violate one of the limitations mentioned above. Additionally, it needs to be taken into account that it's possible to deploy and run that feature in the cloud environment.

resources/references/adr/2020-08-14-implement-individual-sorting.md

@@ -3,14 +3,7 @@ title: Implement individual sorting
 date: 2020-08-14
 area: core
 tags: [repository, dal, entity, sort, product]
---- 
-
-# Implement individual sorting
-
-{% hint style="info" %}
-This document represents an architecture decision record (ADR) and has been mirrored from the ADR section in our Shopware 6 repository.
-You can find the original version [here](https://github.com/shopware/platform/blob/trunk/adr/2020-08-14-implement-individual-sorting.md)
-{% endhint %}
+---
 
 ## Context
 

resources/references/adr/2020-08-14-merchant-registration.md

@@ -3,14 +3,7 @@ title: Merchant registration
 date: 2020-08-14
 area: customer-order
 tags: [merchant, registration, customer-group]
---- 
-
-# Merchant registration
-
-{% hint style="info" %}
-This document represents an architecture decision record (ADR) and has been mirrored from the ADR section in our Shopware 6 repository.
-You can find the original version [here](https://github.com/shopware/platform/blob/trunk/adr/2020-08-14-merchant-registration.md)
-{% endhint %}
+---
 
 ## Context