Skip to content

Conversation

srenon
Copy link
Member

@srenon srenon commented Dec 24, 2017

Description

The SKU by itself is not very useful because for most third-party integration you will need at minimum SKU and qty.

The 'res' is also important because you could write a plugin for Magento\Checkout\Controller\Cart\Add to add more information to the return JSON.

The SKU by itself is not very useful because for most third-party integration you will need at minimum SKU and qty. 

The 'res' is also important because you could write a plugin for Magento\Checkout\Controller\Cart\Add to add more information to the return JSON.
@okorshenko okorshenko self-assigned this Dec 26, 2017
@okorshenko okorshenko added this to the December 2017 milestone Dec 26, 2017
@magento-team magento-team merged commit 6d2f213 into magento:2.2-develop Dec 28, 2017
@koenner01
Copy link
Contributor

Would be handy if this was backported to 2.1 too :)

@koenner01
Copy link
Contributor

However after looking at other places Magento fires events through the trigger, I'm not a fan of dumping all the parameters after each other in the trigger. It would be better to add 1 parameter 'eventData' that contains the seperate variables.
This way you can more easily create a generic handler for the triggered events and the codebase is staying more closely to how the current implementations work

@Ctucker9233
Copy link

Created Backport for this #14898

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants