Releases: scandipwa/catalog-graphql
Custom stock processor removal [Magento 2.4]
What's inside
- Custom stock processor removal
Feature break-down
Custom stock processor removal
The custom stock processor of ScandiPWA was removed. We now use Magento's original one.
Add table prefix support
What's inside
- Add table prefix support
Feature break-down
Add table prefix support
The awesome @santosh-gaggle fixed the table prefix issue. He is awesome!
Custom stock processor removal [Magento 2.3.5]
What's inside
- Custom stock processor removal
Feature break-down
Custom stock processor removal
The custom stock processor of ScandiPWA was removed. We now use Magento's original one.
Magento 2.4 support
What's inside
- Patches for Magento 2.4 support
Feature break-down
Patches for Magento 2.4 support
The following files were changed to match Magento 2.4 API:
src/SearchAdapter/Query/Builder/Match.phpsrc/Model/Resolver/Products/Query/Search.php
Exact module dependencies
What's inside
- Migration to exact module dependencies
- Bug fixes
Feature break-down
Migration to exact module dependencies
Reference to module magento/magento-base of specific Magento 2 version got removed. Instead, dependencies onto specific Magento 2 modules was implemented. This affected etc/module.xml and composer.json file.
Bug fixes
- Patched comments in
.xmlfiles - Removed
authorandsupportsections fromcomposer.jsonin preparation for mono-repo setup
Bug fixes
What's inside
- Catalog price rules patch
- Configurable product variant attributes patch
Feature break-down
Catalog price rules patch
Previously, the customer group was not set on session, now it is. We can make a request by customer group, and if there are catalog-price-rules by customer group applied they will now return correct data.
Configurable product variant attributes patch
The issue described here scandipwa/scandipwa#887 was resolved. The detection detection of PLP / PDP request was not working, now it is. The plugin was added to handle this.
Patch of canonical URLs
What's inside
- Removal of /category and /product from canonical URLs
Feature break-down
Removal of /category and /product from canonical URLs
The canonical URLs were reverted to Magento default implementation. They now support the toggling of them in Stores > Settings > Configuration > Catalog > Catalog > Search Engine Optimization. The properties Use Canonical Link Meta Tag For Categories and Use Canonical Link Meta Tag For Products.
Support for `used_in_product_listing`
What's inside
- Support for
used_in_product_listing
Feature break-down
Support for used_in_product_listing
Previously, there was an issue with too large PLP response due all attributes being returned. To resolve it, the support for attribute property used_in_product_listing has been added.
How it works? For all PLP requests it checks if the attribute has visibility on storefront and used in product listing enabled. Only attributes matching the check are returned.
How to migrate? Go to admin, for attributes you want to be visible on PLP, enable the used_in_product_listing property.
Collection processors removal, product list-widget fixes
What's inside
- Collection processors removal
- Patches to product list-widget
Feature break-down
Collection processors removal
In this release following files in (src/Model/Resolver/Products/SearchCriteria/CollectionProcessor) were removed:
FilterProcessor.phpFilterProcessor/CategoryFilter.phpFilterProcessor/ConditionsFilter.phpFilterProcessor/ConfigurableProductAttributeFilter.phpFilterProcessor/CustomerGroupFilter.phpFilterProcessor/ProductIdFilter.php
Why? Well, since migration to Elasticsearch they... were not used! This means we are back to M2 core filter processors.
Patches to product list-widget
Following issues were resolved: scandipwa/scandipwa#724, scandipwa/scandipwa#835
The implementation made as Collection processor was removed (along-side other processors) and replaced by a plugin, working on the argument value resolving level. This means plugging to Magento\Framework\GraphQl\Query\Resolver\Argument\AstConverter. The solution is not perfect in terms of performance, but unfortunately, implementing it otherwise might break the internal logic of product-widget condition composition. We will wait, to see if Magento team does something about it.
Swatches for aggregations, layered filter logic removal
Since the migration to ES7 means no more MySQL filters, the custom classes responsible for this functionality have been removed.
Additionally the field swatch_data was added to AggregationOptionInterface. Now you can render visual swatches using it.