[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)
@@ -479,6 +480,10 @@
     * [Mocking repositories](resources/references/adr/2023-04-01-mocking-repositories.md)
     * [Disable css autoprefixer](resources/references/adr/2023-04-03-disable-css-autoprefixer.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)
+    * [Stock API](resources/references/adr/2023-05-15-stock-api.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)
     * [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

@@ -5,13 +5,6 @@ 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:
 

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

@@ -5,13 +5,6 @@ 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

@@ -5,13 +5,6 @@ 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.
 To ensure these routes cannot be called accidentally or intentionally without a token, a route parameter is in need to distinguish open routes and those that need a token.

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

@@ -5,13 +5,6 @@ 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:
 

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

@@ -5,13 +5,6 @@ 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.
 This was necessary, because the logic of how the document is rendered has changed a lot. Previously it worked with a simple loop over the line items, now they are rendered recursively.

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

@@ -5,13 +5,6 @@ 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
 
 We need a different extension mechanism besides the well known plugins, that works in cloud and on-prem environments in the same way.

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

@@ -5,13 +5,6 @@ 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
 
 Shop owners should be able to define custom sorting options for product listings and search result pages out of the administration.

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

@@ -5,13 +5,6 @@ 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
 
 We have to provide a registration for merchant.