Return to Answer

added 12 characters in body

Source Link

edited Jun 21, 2016 at 8:15

70.6k
36
190
354

Explanation regarding lack of consistency.

According to Vinai and what Vitaly Korotun told him at some point:

getEvent() is legacy.getEvent() is legacy. Back in Magento 1.0in Magento 1.0 days the event data could not be pulled from the observer directly.the event data could not be pulled from the observer directly.

So if you don't need to get event_name and don't care too much about your code being Magento 1.0 compatible, you can leave out getEvent().

Explanation regarding lack of consistency.

According to Vinai and what Vitaly Korotun told him at some point:

getEvent() is legacy. Back in Magento 1.0 days the event data could not be pulled from the observer directly.

So if you don't need to event_name and don't care too much about your code being Magento 1.0 compatible, you can leave out getEvent().

Explanation regarding lack of consistency.

According to Vinai and what Vitaly Korotun told him at some point:

getEvent() is legacy. Back in Magento 1.0 days the event data could not be pulled from the observer directly.

So if you don't need to get event_name and don't care too much about your code being Magento 1.0 compatible, you can leave out getEvent().

Source Link

created Jun 21, 2016 at 8:06

Raphael at Digital Pianism

70.6k
36
190
354

Explanation regarding lack of consistency.

According to Vinai and what Vitaly Korotun told him at some point:

getEvent() is legacy. Back in Magento 1.0 days the event data could not be pulled from the observer directly.

So if you don't need to event_name and don't care too much about your code being Magento 1.0 compatible, you can leave out getEvent().