Optimization: magento/module-eav is_null change to strict comparison …

[coderimus]

Hello,
This is the one of the optimization PR linked with the is_null() change. I decided to do them per module just to avoid any mistake during delivery and review.
Best regards,
Alex

Description

Micro-optimizations for Magento\EAV
Magento2 has next sniff MicroOptimizations It checks next: is_null must be avoided. Use strict comparison instead.
Some classes are under // @codingStandardsIgnoreFile such as Magento\Eav module models and cannot be checked during static tests. In this PR I replaced is_null with strict comparison only for models in Magento\Eav module.

Fixed Issues (if relevant)

N/A

Manual testing scenarios

N/A

Contribution checklist

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• All automated tests passed successfully (all builds on Travis CI are green)

[orlangur]

@coderimus @ihor-sviziev just for the record, all such occurrences may be fixed all over the code automatically within seconds :) And many other coding style violations as well... Please take into account PRs processing overhead together with other aspects.

[coderimus]

@orlangur thank you for details :) I made several PRs for the same fix divided them per module just to minimalize the % of possible errors during delivery and review. But I see that this was not so good idea because it loads the general flow. I will prepare left fixes for this issue and do one PR for them. Have a good week! :)

[orlangur]

@coderimus no problem, we all are learning here 👍 Thanks for understanding and good luck with your next contributions.