diff --git a/assets/additional_permissions-gui.png b/assets/additionalPermissions-gui.png similarity index 100% rename from assets/additional_permissions-gui.png rename to assets/additionalPermissions-gui.png diff --git a/assets/adr/message_queue_stats.png b/assets/adr/message-queue-stats.png similarity index 100% rename from assets/adr/message_queue_stats.png rename to assets/adr/message-queue-stats.png diff --git a/assets/adr/tideways_benchmark.png b/assets/adr/tideways-benchmark.png similarity index 100% rename from assets/adr/tideways_benchmark.png rename to assets/adr/tideways-benchmark.png diff --git a/assets/audit_log_structure.svg b/assets/auditlog-structure.svg similarity index 100% rename from assets/audit_log_structure.svg rename to assets/auditlog-structure.svg diff --git a/assets/availability_field.png b/assets/availability-field.png similarity index 100% rename from assets/availability_field.png rename to assets/availability-field.png diff --git a/assets/availability_route.png b/assets/availability-route.png similarity index 100% rename from assets/availability_route.png rename to assets/availability-route.png diff --git a/assets/profiler_events.png b/assets/profiler-events.png similarity index 100% rename from assets/profiler_events.png rename to assets/profiler-events.png diff --git a/assets/reverse_proxy_setup.svg b/assets/reverseProxy-setup.svg similarity index 100% rename from assets/reverse_proxy_setup.svg rename to assets/reverseProxy-setup.svg diff --git a/guides/hosting/infrastructure/reverse-http-cache.md b/guides/hosting/infrastructure/reverse-http-cache.md index d21acdb3a5..5236e58fa2 100644 --- a/guides/hosting/infrastructure/reverse-http-cache.md +++ b/guides/hosting/infrastructure/reverse-http-cache.md @@ -24,7 +24,7 @@ In this guide, we will use Varnish as an example for HTTP cache. This setup is compatible from Shopware version 6.4. ::: -![](../../../assets/reverse_proxy_setup.svg) +![](../../../assets/reverseProxy-setup.svg) ### Configure Shopware diff --git a/guides/integrations-api/general-concepts/api-versioning.md b/guides/integrations-api/general-concepts/api-versioning.md index 92a7fae591..4c9e6d25aa 100644 --- a/guides/integrations-api/general-concepts/api-versioning.md +++ b/guides/integrations-api/general-concepts/api-versioning.md @@ -45,17 +45,17 @@ Also, deprecated fields and routes are now shown in the Swagger documentation. H The Swagger API reference now includes the necessary information about the route and field availability. For routes, this can look like this: -![Availability route](../../../assets/availability_route.png) +![Availability route](../../../assets/availability-route.png) Note the availability information. Same for fields, here is an example of how it would look like: -![Availability field](../../../assets/availability_field.png) +![Availability field](../../../assets/availability-field.png) ### API expectations -API expectations can be used as a request header to define necessary conditions for the server side. Example conditions could be the Shopware version, the existence of plugins, or the version of a plugin. There are some examples: +API expectations can be used as a request header to define the necessary conditions for the server side. Example conditions could be the Shopware version, the existence of plugins, or the version of a plugin. There are some examples: ```text GET /api/test diff --git a/guides/plugins/plugins/administration/add-acl-rules.md b/guides/plugins/plugins/administration/add-acl-rules.md index 6c2729d098..f32a579b23 100644 --- a/guides/plugins/plugins/administration/add-acl-rules.md +++ b/guides/plugins/plugins/administration/add-acl-rules.md @@ -61,7 +61,7 @@ For each admin privilege, the needed entity privileges need to be assigned. Depe In addition to the normal `permissions`, which represent CRUD functionality, there are also `additional_permissions`. These are intended for all functions that cannot be represented by CRUD. -![Additional permissions GUI](../../../../assets/additional_permissions-gui.png) +![Additional permissions GUI](../../../../assets/additionalPermissions-gui.png) The `additional_permissions` have their own card below the normal permissions grid. An example for `additional_permissions` would be: "clearing the cache". This is an individual action without CRUD functionalities. The key is still used for grouping. Therefore the role can be individual and does not have to follow the scheme. diff --git a/guides/plugins/plugins/framework/event/finding-events.md b/guides/plugins/plugins/framework/event/finding-events.md index d1198a63e5..d8fc61ddab 100644 --- a/guides/plugins/plugins/framework/event/finding-events.md +++ b/guides/plugins/plugins/framework/event/finding-events.md @@ -229,7 +229,7 @@ Since Shopware is built upon the Symfony framework, it also grants access to the Using the profiler, you can easily find all fired events in the current request. You can do so by opening up the profiler and clicking on the "Events" tab on the left. -![](../../../../../assets/profiler_events.png) +![](../../../../../assets/profiler-events.png) There you will find all events that were fired in the current request including their respective name to be used. diff --git a/products/extensions/b2b-suite/guides/core/audit-log.md b/products/extensions/b2b-suite/guides/core/audit-log.md index 44fa0a5c27..4677fb2107 100644 --- a/products/extensions/b2b-suite/guides/core/audit-log.md +++ b/products/extensions/b2b-suite/guides/core/audit-log.md @@ -14,7 +14,7 @@ nav: The B2B Suite provides a general audit log that can be implemented in every component. The audit log component can save different log types and author information like first name, last name, and email. It provides a one-to-many association index. The database structure is described in the graphic below: -![image](../../../../../assets/audit_log_structure.svg) +![image](../../../../../assets/auditlog-structure.svg) As you can see, the database structure is very flat. In the `b2b_audit_log` table, we save a log type and a serialized *AuditLogValueEntity*. All required author information is saved in the `b2b_audit_log_author` table. diff --git a/resources/references/adr/2021-11-09-increment-pattern.md b/resources/references/adr/2021-11-09-increment-pattern.md index eb72a46690..89ff06c434 100644 --- a/resources/references/adr/2021-11-09-increment-pattern.md +++ b/resources/references/adr/2021-11-09-increment-pattern.md @@ -37,7 +37,7 @@ So we implement a new gateway with the following methods: This then enables the following functional flow: -![](../../../assets/adr/message_queue_stats.png "Message queue stats gateway") +![](../../../assets/adr/message-queue-stats.png "Message queue stats gateway") Furthermore, it should also be possible to completely disable the message queue stats or any pool via config file. diff --git a/resources/references/adr/2022-03-25-profiler-integrations.md b/resources/references/adr/2022-03-25-profiler-integrations.md index f429cac785..2607761293 100644 --- a/resources/references/adr/2022-03-25-profiler-integrations.md +++ b/resources/references/adr/2022-03-25-profiler-integrations.md @@ -116,7 +116,7 @@ class CartCalculator ``` These spans are then displayed in the timeline of the corresponding profilers: -![](../../../assets/adr/tideways_benchmark.png "Tideways benchmark") +![](../../../assets/adr/tideways-benchmark.png "Tideways benchmark") Which profiler should be used in the system can be configured via `config/packages/*.yaml`: