Magento DevBlog - Page 9

Service contracts (defined using PHP interfaces) are currently included in same module that implements the interfaces and are versioned with the rest of Magento. One strategy under consideration is to separate into two modules the PHP interfaces that define service contracts and their implementation. The version number of the modules holding the service contracts would then only change if the contract changes. This provides more stability for extension developers.

If you have tried to implement a payment integration in Magento, you might have had a trouble with the sale (authorize & capture) payment operation. This post describes how the Place an Order flow is implemented in Magento, the “bridge” between Magento and payment service providers, and how to implement the sale operation when using custom payment methods without breaking the Place an Order flow.

Magento purchased the Bluefoot CMS extension from Gene Commerce (thanks guys!) and are merging it into Magento 2.3 Enterprise Edition as a part of the standard core product. This extension provides a drag-and-drop interface for creating rich content with embedded widgets. This blog post describes the current integration vision (this vision is subject to change) and the capabilities that both theme developers and Admin users will have. Feedback is welcome!

Open webinar devoted to Versioning and Backward Compatible development for Magento 2 will take place on May 16, 2017 10:00 AM CDT.

You can register for the webinar at the following link - https://attendee.gotowebinar.com/register/6002105715587090435

I like microservices – I have used them on some big projects. But should Magento move to a microservice architecture? I think Magento should become microservice capable, but not mandate them. I like how a recent tweet put it “Microservices have yielded simpler components – but more complicated systems”.

Magento Community Engieering Team is accepting Pull Requests for 2.1.x patch releases.

Discussions from Magento DevExchange on frontend development at Imagine 2017.

At the end of the Imagine conference this year, instead of the traditional bar camp, Sherrie Rohde tried something new – DevExchange. Rather than presentations, groups of developers shared there experiences and thoughts on a current hot topic. The first topic I sat in on (well, stood up for really – there were almost as many people standing as sitting) was on Headless Magento.

We published the list of basic design truths that our team agrees to.

This post is first in a series talking about planned improvements to the persistence layer in Magento 2. Currently, Magento 2 “business logic” has SQL queries directly embedded into the code. One of the areas of active investigation within Magento is to improve the separation of business logic from persistence logic. This blog post is a high-level introduction to the scope of work planned. This work is still reasonably early in the research cycle.

Magento Dependency Injection implementation comes with the very powerful concept of Virtual Types.  However, with great power comes great responsibility. Virtual types provide a declarative way to create multiple instances of a single PHP class, each with a different constructor argument. This allows developers to implement new functionality or change Magento behavior with less code and so with fewer bugs. As with any other subject in programming, a good naming of virtual types allows writing code that is easy to understand and support. In this post we describe the future naming scheme that Magento will be using from now on for naming of virtual types. Feedback is welcome!

You can buy extensions from the online Magento Marketplace (marketplace.magento.com) and they appear in your Composer repository for download (repo.magento.com), but how does this work behind the scenes? Why do I need to go through Marketplace to get free extensions, but not to get Magento Community Edition (CE)? And why does Magento Enterprise Edition (EE) appear only after I pay? This post describes the relationship between the Marketplace online store, the Composer repository, and the entitlements that link the two.

As I shared at MagentoLive France this morning, our community is now able to help us prioritize issues through the use of GitHub's "Reactions" feature.

In the introductory post to the Magento developer blog, Ben Marks mentioned a number of developer-focused initiatives which we are implementing this year. Rather than keep you all guessing, I'd like to share our roadmap for these initiatives.

The place for developer-focused news direct from the source.