In the last article of our series, we covered the "class preference" feature of Magento's object manager. This week we'll cover a similar, but more selective, class replacement system built into Magento 2. While this article should be accesible as a stand-alone tutorial for
astormToday we're going to explore the "class preference" feature of Magento 2's object-manager/dependency-injection system. While this feature is a direct descendant of Magento 1's class rewrite system, it ends up playing a different role in Magento 2. Where Magento 1's class rewrites were aimed
astormOn a "what they do level", interfaces are pretty simple. Consider the following PHP class
astormThis week's article is the second in a series discussing Magento 2's object system. Last time we covered the basics of Magento's object manager. This week we're going explain why you'll rarely use Magento's object manager, as well as Magento's implementation of the popular
astormMagento 2 brings a slew of changes to the table for an experienced Magento 1 programmer. While you can still see bits and pieces of Magento 1 (EAV, areas, blocks, etc.), the new Magento 2 core team has spent the last few years
astormToday we're going to give you a quick overview of PHP type hints. While the debate over how strongly PHP should be typed rages on, many PHP frameworks have started using type hints as metadata for implementing features like dependency injection. Whatever you think
astorm