[create-pull-request] automated change (#1630)

Co-authored-by: shopwareBot <[email protected]>

resources/references/adr/2020-08-21-unified-notification-titles.md

@@ -46,7 +46,7 @@ For more information on snippets deleted in this course see CHANGELOG-6.3.md
 
 * Create error notification
 
-```javascript
+```js
 this.createNotificationError({
     message: this.$tc('sw-module.messageError')
 });
@@ -59,7 +59,7 @@ this.createNotificationError({
 
 * Avoid cheap solutions like 
 
-```javascript
+```js
 this.createNotificationError({
     message: err
 });

resources/references/adr/2020-08-28-import-acl-privileges-from-other-roles.md

@@ -24,7 +24,7 @@ To avoid duplication of these privileges we use a helper function. These
 function returns all privileges from the other module dynamically. You can
 use it directly in the privileges:
 
-```javascript
+```js
 Shopware.Service('privileges')
     .addPrivilegeMappingEntry({
         category: 'permissions',

resources/references/adr/2021-12-07-admin-extension-api-standards.md

@@ -29,7 +29,7 @@ An app wants to render a custom iFrame in a card on the dashboard. The "location
 
 The app want to render different views depending on the "location" of the iFrame. So the app developer can render the correct view depending on the "locationID":
 
-```javascript
+```js
 if (sw.location.is('sw-dashboard-example-app-dashboard-card')) {
     renderDashboardCard();
 }
@@ -46,7 +46,7 @@ Developers can extend existing areas or create new areas in the administration w
 
 An app wants to add a new tab item to a tab-bar. In the administration are many tab-bars available. So the developer needs to choose the correct "positionID" to determine which tab-bar should be extended. In this example the developer adds a new tab item to the tab-bar in the product detail page.
 
-```javascript
+```js
 sw.ui.tabs('sw-product-detail').addTabItem({ ... })
 ```
 
@@ -59,7 +59,7 @@ In most cases developers will directly use the extension capabilities of the UI
 
 To give them more flexibility we introduce a feature named "Component Sections". These are sections where any extension developer can inject components. These components are prebuilt and they can also contain custom render views with iFrames. The developer needs to use the feature and choose the matching positionID for the component position. 
 
-```javascript
+```js
 // Adding a card before the manufacturer card with custom fields entries.
 sw.ui.componentSection('sw-manufacturer-card-custom-fields__before').add({
     // The Extension-API provides different components out of the box

resources/references/adr/2023-02-27-native-extension-system-with-vue.md

@@ -29,7 +29,7 @@ Our main idea for the template part was to use native Vue components named sw-bl
 
 For the script and logic part, we aimed to use the Composition API. Before returning all the component data and methods, we would provide a hook point for plugins so they could modify or inject everything they want.
 
-```javascript
+```js
 // The original component
 <script setup lang="ts">
 // Hook for providing extensibility

resources/references/adr/2023-05-10-experimental-features.md

@@ -108,7 +108,7 @@ To do so add the `Experimental` tag to the OpenApi definition of the route and a
 
 Modules, Components, Services, etc. can be marked as experimental, meaning that they are not covered by the backwards compatibility promise.
 
-```javascript
+```js
 /**
  * @experimental stableVersion:v6.6.0
  */

resources/references/adr/2023-09-06-feature-property-for-experimental-anotation.md

@@ -57,7 +57,7 @@ class testClass()
 ```
 js
 
-```javascript
+```js
 /**
  * @experimental stableVersion:v6.6.0 feature:WISHLIST
  */