mirror of
https://github.com/Sylius/Sylius.git
synced 2026-07-14 17:10:53 +00:00
[ADR][API] Update ADR for providing locales after changing the approach
This commit is contained in:
parent
46ad6e19ef
commit
4e82e09fdf
1 changed files with 7 additions and 6 deletions
|
|
@ -1,7 +1,8 @@
|
||||||
# Using data provider for getting available locales in active channel for shop user
|
# Using Doctrine Collection extension for getting available locales in active channel for shop user
|
||||||
|
|
||||||
* Status: proposed
|
* Status: accepted
|
||||||
* Date: 2021-07-05
|
* Propose date: 2021-07-05
|
||||||
|
* Update date: 2022-03-15
|
||||||
|
|
||||||
## Context and Problem Statement
|
## Context and Problem Statement
|
||||||
Customer should have access only to locales available in their channel
|
Customer should have access only to locales available in their channel
|
||||||
|
|
@ -16,11 +17,11 @@ Customer should have access only to locales available in their channel
|
||||||
|
|
||||||
### Using Data Provider
|
### Using Data Provider
|
||||||
|
|
||||||
* Good, because we already have this approach for older resources
|
|
||||||
* Good, because it is easy to implement
|
* Good, because it is easy to implement
|
||||||
* Bad, because using data providers omits extra Doctrine extensions like pagination
|
* Bad, because using data providers omits extra Doctrine extensions like pagination
|
||||||
|
|
||||||
## Decision Outcome
|
## Decision Outcome
|
||||||
|
|
||||||
Chosen option: Using Data Provider
|
Chosen option: **"Using Doctrine Collection extension"**
|
||||||
Shops shouldn't have many locales for each channel, so lack of a pagination is smaller problem than creating overcomplicated query in Doctrine Collection extension
|
|
||||||
|
This option is consistent with current approach and does not omit Doctrine extensions like pagination.
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue