Add option to index child attributes or not#2443
Add option to index child attributes or not#2443fredden wants to merge 7 commits intoSmile-SA:2.10.xfrom
Conversation
|
Hi @fredden, having such a config globally is not enough for me, I'd like to be able to also control which attributes are mergeable, and which are not, as it's done "hardcoded" actually, but with the ability to inject the list through DI. Can you rework this PR ? Anyway, thank you for proposing it. Best regards |
|
Hi @romainruaud. Thanks for the feedback. Making the list of I think having the setting exposed in the admin makes more sense than via dependency injection though. This way, if a website administrator adds a new attribute, they'll be able to select its index status right away, and not require a deployment to set this. With an admin configuration option per attribute, I can see it being a chore marking each and every attribute individually as indexable or not; having a global toggle would help then - which is what's being introduced here. What do you think about putting this global toggle in for now, and working on getting the list configurable as a separate task? |
|
Thanks @robaimes. I've updated this pull request to be compatible with the changes introduced in #2465. @romainruaud I still think that this should be merged, and the list of attributes should be set in admin configuration (not via dependency injection) as a separate task / feature. |
|
Hi @rbayet. What can I do to help get this merged in? |
While working with bundle products on a website, the merchant wants to only include attributes of the parent/bundle product not any of its options/children. This configuration option adds the ability for website administrators to make this decision. By default, the existing behaviour is preserved.