Skip to content

Commit 7aaee2c

Browse files
github-actions[bot]shopwareBot
github-actions[bot]
and
shopwareBot
authored
[create-pull-request] automated change (#1195)
Co-authored-by: shopwareBot <[email protected]>
1 parent a121efd commit 7aaee2c

File tree

74 files changed

+226
-228
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

74 files changed

+226
-228
lines changed

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

+1-1
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Implement architecture decision records
33
date: 2020-06-25
44
area: core
55
tags: [adr, workflow]
6-
---
6+
---
77

88
# Implement architecture decision records
99

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

+1-1
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Get control of association clone behavior as developer
33
date: 2020-07-02
44
area: core
55
tags: [repository, entity, clone, flag, association]
6-
---
6+
---
77

88
# Get control of association clone behavior as developer
99

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

+1-1
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Implement sales channel context token requirement for store-api and sales
33
date: 2020-07-02
44
area: core
55
tags: [context, token, sales-channel, store-api, sales-channel-api, api]
6-
---
6+
---
77

88
# Implement sales channel context token requirement for store-api and sales-channel-api
99

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

+1-1
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Implement new changelog
33
date: 2020-08-03
44
area: core
55
tags: [changelog]
6-
---
6+
---
77

88
# Implement new changelog
99

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

+1-1
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Document template refactoring
33
date: 2020-08-12
44
area: customer-order
55
tags: [document, template, twig]
6-
---
6+
---
77

88
# Document template refactoring
99

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

+2-2
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Implement app system inside platform
33
date: 2020-08-12
44
area: core
55
tags: [app, cloud]
6-
---
6+
---
77

88
# Implement app system inside platform
99

@@ -56,7 +56,7 @@ Additionally, the storefront theme files (JS and CSS) only need to be accessed d
5656

5757
* [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.
5858

59-
* [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.
59+
* [Storefront Customizations](/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.
6060
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.
6161

6262
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

+1-1
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Implement individual sorting
33
date: 2020-08-14
44
area: core
55
tags: [repository, dal, entity, sort, product]
6-
---
6+
---
77

88
# Implement individual sorting
99

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

+1-1
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Merchant registration
33
date: 2020-08-14
44
area: customer-order
55
tags: [merchant, registration, customer-group]
6-
---
6+
---
77

88
# Merchant registration
99

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

+5-6
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Notification titles are pre-defined and make use of the global namespace
33
date: 2020-08-21
44
area: administration
55
tags: [administration, notification]
6-
---
6+
---
77

88
# Notification titles are pre-defined and make use of the global namespace
99

@@ -14,8 +14,8 @@ You can find the original version [here](https://github.com/shopware/shopware/bl
1414

1515
## Context
1616

17-
* Creating notifications messages in the administration caused the effort of making up not only a title but a message too.
18-
This has led to inconsistent notification appearances. In some cases the notification message simply duplicated the title,
17+
* Creating notification messages in the administration caused the effort of making up not only a title but a message too.
18+
This has led to inconsistent notification appearances. In some cases, the notification message simply duplicated the title;
1919
others wore the module's name as a title and so on.
2020

2121
* Now, since it is a set design decision to use the following four types of notification as titles at the same time,
@@ -39,7 +39,7 @@ it is just logical to make use of the global namespace and manage notification t
3939
* By introducing the global namespace as early as in the `notification.mixin.js`
4040
it is now unnecessary to define individual titles when implementing notifications within a module.
4141
* Notifications from now on only require a "notification message" and thus the creation of only snippet within each snippet file (en-GB and de-DE).
42-
* Consequently a whole bunch of unnused snippets have been removed.
42+
* Consequently, a bunch of unused snippets have been removed.
4343
For more information on snippets deleted in this course see CHANGELOG-6.3.md
4444

4545
### Examples
@@ -69,7 +69,7 @@ this.createNotificationError({
6969
* Messages should be translatable, precise and not redundant. An error notification's title literally says: "Error" - no need in repeating that.
7070
Better find and present information on what exactly went wrong.
7171

72-
* Make use of success notifications, but make them carry useful information, by e.g. including counters.
72+
* Make use of success notifications, but make them carry useful information, by e.g., including counters.
7373

7474
* Make use of info and warning notifications to keep users informed about things that are ongoing or need a closer look!
7575

@@ -81,4 +81,3 @@ It would cross the design idea of unified titles though and should only be consi
8181
> *When creating notifications, just decide on the correct type of notification,
8282
add a meaningful message, don't waste even a thought on creating a title...
8383
And you're done!*
84-

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

+1-1
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Import ACL privileges from other roles
33
date: 2020-08-28
44
area: administration
55
tags: [acl, privileges, dependency, administration]
6-
---
6+
---
77

88
# Import ACL privileges from other roles
99

‎resources/references/adr/2020-09-08-custom-field-label-loading-in-storefront.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: CustomField label loading in storefront
33
date: 2020-09-08
44
area: storefront
55
tags: [custom-fields, storefront, snippets]
6-
---
6+
---
77

88
# CustomField label loading in storefront
99

‎resources/references/adr/2020-09-17-the-best-practice-to-always-re-fetch-the-data-after-saving.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: The best-practice to always re-fetch the data after saving
33
date: 2020-09-17
44
area: administration
55
tags: [administration, data-handling]
6-
---
6+
---
77

88
# The best-practice to always re-fetch the data after saving
99

‎resources/references/adr/2020-11-19-dal-join-filter.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: DAL join filter
33
date: 2020-11-19
44
area: core
55
tags: [dal, join-filter, negated-filter, criteria]
6-
---
6+
---
77

88
# DAL join filter
99

‎resources/references/adr/2020-11-20-add-login-required-annotation.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Add the login required annotation
33
date: 2020-11-20
44
area: core
55
tags: [annotation, login, customer, api, store-api]
6-
---
6+
---
77

88
# Add the login required annotation
99

‎resources/references/adr/2020-11-25-decoration-pattern.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Decoration pattern
33
date: 2020-11-25
44
area: core
55
tags: [decoration, plugin, interface, abstraction]
6-
---
6+
---
77

88
# Decoration pattern
99

‎resources/references/adr/2020-12-02-removing-api-version.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: API version removal
33
date: 2020-12-02
44
area: core
55
tags: [api, versioning, deprecation]
6-
---
6+
---
77

88
# API version removal
99

0 commit comments

Comments
 (0)