magento / magento/catalog-storefront
Document: store configuration propagation to Storefront
Open
@buskamuza is already working on this.
Since Jul 15, 2020.
internal
- Dominant language
- PHP
- Stars
- 7
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
How to resolve cases where Magento Admin configuration affects a lot of data on SF side (e.g., Base Media URL, SEO canonical url?
Generic idea:
- Decide whether logic is handled on the side of PIM + full reindex, or on the side of SF by calculating full data, based on expected frequency of the config option modifications
- Settings that impact data returned by SF are part of SF
- Settings that impact UI only, should be represented as a separate service (additional service per SF service that needs UI settings)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.