-
Notifications
You must be signed in to change notification settings - Fork 7
feat: [SFCC-468] Exposed variation attribute as a site preference in the Algolia BM module #245
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
cartridges/int_algolia_sfra/cartridge/scripts/hooks/order/algoliaHooks.js
Outdated
Show resolved
Hide resolved
Reverted changes to end-to-end test file
9629378 to
3cd937e
Compare
…ord as a site preference in BM
73ffb11 to
3a8c8d0
Compare
86930e2 to
e6a7634
Compare
cartridges/bm_algolia/cartridge/templates/resources/algolia.properties
Outdated
Show resolved
Hide resolved
cartridges/bm_algolia/cartridge/templates/resources/algolia.properties
Outdated
Show resolved
Hide resolved
cartridges/bm_algolia/cartridge/templates/resources/algolia.properties
Outdated
Show resolved
Hide resolved
…edRecordModel_GroupingAttribute
…se-variation-attribute-as-site-preference
Created new site preference
AttributeSlicedRecordModel_GroupingAttributewhich takes the place of the hardcoded 'color' value for the grouping variation attribute for the "Attribute-sliced" record model.The Algolia BM module was updated in such a way that the value of the new site preference is only editable if the user selectes the "Attribute-sliced" record model.
The code throws an error and returns if the user selected the "Attribute-sliced" record model but haven't set
AttributeSlicedRecordModel_GroupingAttributeas well.Testing notes
system-objecttype-extensions.xmlfirst!variationModel.getProductVariationAttribute('<attribute>')won't return anything and indexing falls back to the master-type record (all variations in the same record).