How do I approach to fixing bugs of Magento 2 code in the custom project?

by Alexey Shchur   Last Updated December 07, 2017 11:09 AM

For example, this bug: What if I'm building a custom project, based on current Magento 2.2.0 version, and I face with this bug in it's code.

I know that it will be fixed in the upcoming release (2.2.2), however, I need the custom project fixed right now.

How do I approach to fixing this? What comes to my mind, is to rewrite the involved Model in a custom module.

Is this the best practice to deal with this situation, or there are some smarter ways?

Tags : magento2 bug

Related Questions

Magento 2.1.6 sampleData broken images by default

Updated April 21, 2017 09:09 AM

Data migration in Magento 2

Updated November 15, 2017 07:09 AM