GroupBy editable in Recommendations by Cross Selling

[iago1501]

What problem is this solving?

We have a limitation in Recommendation queries where we always group by products, but, some customers, especially when talking about fashion segments, want to show also individual SKUs instead, this feature is responsible for allowing that.

Also, there's another limitation presented here that we are trying to cover. When grouping by products and calling the catalog cross selling API, we do a reduced search, in this reduced search, the total quantity of products returned is limited by 12, but, if we don't use this parameter the limit is 50, so, we are also increasing the possibility of the number of products returned by this query

How should this be manually tested?

Workspace

These queries in app vtex.search-graphql

query ProductRecommendations(
  $identifier: ProductUniqueIdentifier
  $type: CrossSelingInputEnum
  $groupBy: CrossSelingGroupByEnum
){
  productRecommendations(identifier: $identifier, type: $type, groupBy: $groupBy) {
    cacheId
    productId
    productName
    productReference
  }
}

{
  "identifier": {
    "field": "id",
    "value": "177"
  },
  "type": "similars",
  "groupBy": PRODUCT
}

 
query ProductsByIdentifier(
  $field: ProductUniqueIdentifierField!
  $values: [ID!]
){
  productsByIdentifier(field: $field, values: $values) {
    recommendations(groupBy: PRODUCT) {
      similars{
        cacheId
      	productId
    		productName
    		productReference
      }
    }
  }
}

{
  "field": "id",
  "values": [21]
}

Screenshots or example usage

Type of changes

✔️	Type of Change
_	Bug fix
✔️	New feature
_	Breaking change
_	Technical improvements

Notes

Complements with: vtex-apps/search-graphql#135

[vtex-io-ci-cd]

Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖

Please select which version do you want to release:

• Patch (backwards-compatible bug fixes)

• Minor (backwards-compatible functionality)

• Major (incompatible API changes)

And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.

• No thanks, I would rather do it manually 😞

[pedrobernardina]

@iago1501

I've tested the queries on your WS.
LGTM 🎉

[vtex-io-ci-cd]

Your PR has been merged! App is being published. 🚀
Version 1.68.0 → 1.69.0

After the publishing process has been completed (check #vtex-io-releases) and doing A/B tests with the new version, you can deploy your release by running:

vtex deploy vtex.search-resolver@1.69.0

After that your app will be updated on all accounts.

For more information on the deployment process check the docs. 📖