Riccardo Tempestaro.meet-magento.com/wp-content/uploads/2017/10/Riccardo...Riccardo Tempesta @...

Riccardo Tempesta @ MageSpecialist / Twitter: @RicTempesta #MM17RO

Riccardo TempestaThe right tools for the right job in Magento 2


THE RIGHT TOOLS FOR THE RIGHT JOB (OR: SURVIVING MAGENTO 2 CODING)

The daily work of a [Magento 2] developer consists of two main job types

Debuggingexisting features

Creatingnew features

Your code3rd party’s

(or core) code

A B


We will focus on this

Debuggingexisting features

Creatingnew features


(or core) code

A B



A SHORT HINT ON: CREATING FEATURES

You will need these thingies:

PHPStorm IDE

Vagrant (or Docker ?)

GIT

Magicento2

Code generators

A lot of free time…




Magicento 2 and Code Generators because: Magento 2 requires a bit of boilerplate code A typo is always lurking somewhere Your time is not free The amount of required code may be considerable You may need a social life… (not sure about this)




STARTING YOUR PROJECT:Mage2Gen can create a whole module skeleton with a minimum effort.It is an online/commandline tool available at: https://mage2gen.com/


DEVELOPING YOUR PROJECT:Magicento can create controllers, modules, plugins, observers and lots of other coding entities in few clicks.Convenient code hints and autocompletition.

Your client does not always understand how complex this job is!So make it as simple as possible!

REMEMBER


A SHORT HINT ON: CREATING FEATURESExample of code complexity: Magento 1 vs. Magento 2

Magento 1 – DB Models: Model ResourceModel Collection Install / Upgrade scripts config.xml

Magento 2 – DB Models: Model Data Model ResourceModel Collection Install / Upgrade scripts Repository Repository Interface Model Interface Data Interface Preferences Getters / Setters in DataInterface

Total involved files: 4-5 Total involved files: 10-11



A SHORT HINT ON: CREATING FEATURESYou will need: MageSpecialist Code Monkey


magento@somewhere:~$ php bin/magento msp:cm:crud My_Module Myentity mydatabasetable

● Model● Data Model● DataModel Interface● Resource Model● Collection● Repository● Repository Interface● Registry

● di.xml configuration● Getters● Setters● Repository getters based

on table indexes● Fully Magento2

codestyling compliant

Starting from a database table it can create:

https://github.com/magespecialist/m2-MSP_CodeMonkey


https://github.com/staempfli/magento2-phpstorm-templatesTwitter: @Jalogut

A SHORT HINT ON: MORE ADVANCED TOOLS


PhpStorm Magento2 Templatesfrom Juan Alonso @ StaempfliHigh M2 coding standard compliance.

Ultimate Magento2 module creatorfrom Marius Strajeru

https://github.com/UltimateModuleCreator/Umc_BaseTwitter: @MariusStrajeru

Remember:you owe a beerto both of them

https://github.com/staempfli/magento2-phpstorm-templates


DEBUGGING

DEBUGGING & REVERSE ENGINEERINGbe honest… they are the actual 99% work of a developer



(or core) code


DEBUGGING FEATURES


Common scenario when you’re debugging your code:

You do not know where the broken piece of code may be.

It is very hard to let the client understand that debugging is part (actually: the

most) of developing, so:

You probably do not have any of the project’s budget lef;

Plus, you have a very short time to fix it!

You did not write any kind of test… We know it, do not lie on this!

Stack Exchange is offline.


DEBUGGING FEATURES


Common scenario when you’re debugging 3rd party’s code:

You have no clue about the how the work’s engineered.

You still do not know where the broken piece of code is.

You hope the programmer who worked on that code before you did not touch the

core.

The programmer who created that feature is now probably on permanent vacation

and/or does not speak a single word of your language!

Stack Exchange is still offline…


HOPE IT’S NOT A MESS OF

SPAGHETTI CODE


“I’ve seen PHP code you people wouldn’t believe…”


DEBUGGING FEATURES


Debugging process can be tricky in Magento 2.

Magento 2 has lots of new ways to intercept and change the standard core behaviour...

(I mean without changing the core! Do not try this at home!)

Magento 1 rewriting tools

Rewrites

Routes hijacking

Observers

Layout updates

Magento 2 rewriting tools

Preferences

Routes hijacking

Observers

Layout updates

Stackable plugins (after, before, around)

Extension attributes

…


DEBUGGING FEATURES


FINDING THE PIECE OF CODE YOU NEED CAN BE OFTEN CHALLENGING AND TIME

CONSUMING.



DEBUGGING FEATURES

So the hard part is simply

FIND SOME PIECE OF CODE DOING SOMETHING SOMEHOW SOMEWHERE

and, once found

FIX SOMETHING BROKEN SOMEWHERE WITHSOME THING YOU WILL DO SOMEHOW

As easy as pie… isn’t it?


PhpStorm as IDE

MSP DevTools

To find out where the code is

PHP Xdebug

To find out what’s wrong with the code

GIT bisect

To find out when you broke it


DEBUGGING FEATURES



DEBUGGING FEATURES: MSP DEVTOOLS

Magento 1 & Magento 2 support

Free github project

Chrome extension

Chrome inspector integration

PHPStorm integration


DEBUGGING FEATURES: PHP X-DEBUG Suspend code execution

Inspect variables

Log results

Runtime variables value change

PHP Storm integrates it

You can do the same with “var_dump”, “print_r” and “echo”, but

everytime you do that, a programmer dies somewhere!


MEH IZ PROGRAMMAHPLZ DON’T KILL MEH


DEMO #1



PHP Storm MSP DevTools Xdebug


DEBUGGING FEATURES: GIT BISECT

A typical customer’s bug report is like:

If you manage to understand what is actually broken you can use GIT bisect.

So you just need to know:

what the broken features is and

when it was working for the last time.


“Yesterday all was working on the website, today nothing works! Fix it!!11!1!!”


DEBUGGING FEATURES: GIT BISECT


Works like this


DEMO #2


Git bisect




GIT BISECT!

BAD COMMIT!OH NO!

SO BUGFOUND! RESTORED!

WOW!



THANK YOU!

KEEP CALM AND

I WILL ANSWERYOUR QUESTIONS

Github:MageSpecialist

Twitter:@RicTempesta

Riccardo Tempestaro.meet-magento.com/wp-content/uploads/2017/10/Riccardo...Riccardo Tempesta @...

Documents

Transcript of Riccardo Tempestaro.meet-magento.com/wp-content/uploads/2017/10/Riccardo...Riccardo Tempesta @...