Why do we need parent identities on frontend?
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 12.2k
- Forks
- 9.4k
- PR merge metrics
- No merged PRs in 30d
Description
I've noticed that we have plugin `\Magento\ConfigurableProduct\Model\Plugin\ProductIdentitiesExtender::afterGetIdentities` that is responsible to add parent tags for each child product. For example, that makes the product listing page much slower because we need to load the parent for each product on the page.
Why do we really need that on frontend? I tested and it PURGE cache for all child products when configurable product is saved.
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.
Research direction
Start with Magento\ConfigurableProduct\Model\Plugin\ProductIdentitiesExtender::afterGetIdentities and trace how parent identities are used for frontend cache invalidation. Determine whether those identities are required, then document the impact on product listing performance and cache purging; the issue is complete when the behavior and an agreed change are clearly established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100