What is the benefit of assigning null to some parameters in construct?












1















Not sure if it is Magento related question. But need to understand this.



I have seen some of the parameters in construct are assigned to null value.



For example:



/**
* Initialize dependencies.
*
* @param MagentoFrameworkModelContext $context
* @param MagentoFrameworkRegistry $registry
* @param MagentoFrameworkApiExtensionAttributesFactory $extensionFactory
* @param AttributeValueFactory $customAttributeFactory
* @param MagentoSalesModelOrderFactory $orderFactory
* @param MagentoStoreModelStoreManagerInterface $storeManager
* @param MagentoCatalogApiProductRepositoryInterface $productRepository
* @param MagentoFrameworkModelResourceModelAbstractResource $resource
* @param MagentoFrameworkDataCollectionAbstractDb $resourceCollection
* @param array $data
* @param MagentoFrameworkSerializeSerializerJson|null $serializer
* @SuppressWarnings(PHPMD.ExcessiveParameterList)
*/
public function __construct(
MagentoFrameworkModelContext $context,
MagentoFrameworkRegistry $registry,
MagentoFrameworkApiExtensionAttributesFactory $extensionFactory,
AttributeValueFactory $customAttributeFactory,
MagentoSalesModelOrderFactory $orderFactory,
MagentoStoreModelStoreManagerInterface $storeManager,
MagentoCatalogApiProductRepositoryInterface $productRepository,
MagentoFrameworkModelResourceModelAbstractResource $resource = null,
MagentoFrameworkDataCollectionAbstractDb $resourceCollection = null,
array $data = ,
MagentoFrameworkSerializeSerializerJson $serializer = null
) {
parent::__construct(
$context,
$registry,
$extensionFactory,
$customAttributeFactory,
$resource,
$resourceCollection,
$data
);
$this->serializer = $serializer ?: MagentoFrameworkAppObjectManager::getInstance()
->get(MagentoFrameworkSerializeSerializerJson::class);
$this->_orderFactory = $orderFactory;
$this->_storeManager = $storeManager;
$this->productRepository = $productRepository;
}


MagentoFrameworkSerializeSerializerJson $serializer = null is assigned to null. And in the function it is assigned to object.



$this->serializer = $serializer ?: MagentoFrameworkAppObjectManager::getInstance()
->get(MagentoFrameworkSerializeSerializerJson::class);









share|improve this question



























    1















    Not sure if it is Magento related question. But need to understand this.



    I have seen some of the parameters in construct are assigned to null value.



    For example:



    /**
    * Initialize dependencies.
    *
    * @param MagentoFrameworkModelContext $context
    * @param MagentoFrameworkRegistry $registry
    * @param MagentoFrameworkApiExtensionAttributesFactory $extensionFactory
    * @param AttributeValueFactory $customAttributeFactory
    * @param MagentoSalesModelOrderFactory $orderFactory
    * @param MagentoStoreModelStoreManagerInterface $storeManager
    * @param MagentoCatalogApiProductRepositoryInterface $productRepository
    * @param MagentoFrameworkModelResourceModelAbstractResource $resource
    * @param MagentoFrameworkDataCollectionAbstractDb $resourceCollection
    * @param array $data
    * @param MagentoFrameworkSerializeSerializerJson|null $serializer
    * @SuppressWarnings(PHPMD.ExcessiveParameterList)
    */
    public function __construct(
    MagentoFrameworkModelContext $context,
    MagentoFrameworkRegistry $registry,
    MagentoFrameworkApiExtensionAttributesFactory $extensionFactory,
    AttributeValueFactory $customAttributeFactory,
    MagentoSalesModelOrderFactory $orderFactory,
    MagentoStoreModelStoreManagerInterface $storeManager,
    MagentoCatalogApiProductRepositoryInterface $productRepository,
    MagentoFrameworkModelResourceModelAbstractResource $resource = null,
    MagentoFrameworkDataCollectionAbstractDb $resourceCollection = null,
    array $data = ,
    MagentoFrameworkSerializeSerializerJson $serializer = null
    ) {
    parent::__construct(
    $context,
    $registry,
    $extensionFactory,
    $customAttributeFactory,
    $resource,
    $resourceCollection,
    $data
    );
    $this->serializer = $serializer ?: MagentoFrameworkAppObjectManager::getInstance()
    ->get(MagentoFrameworkSerializeSerializerJson::class);
    $this->_orderFactory = $orderFactory;
    $this->_storeManager = $storeManager;
    $this->productRepository = $productRepository;
    }


    MagentoFrameworkSerializeSerializerJson $serializer = null is assigned to null. And in the function it is assigned to object.



    $this->serializer = $serializer ?: MagentoFrameworkAppObjectManager::getInstance()
    ->get(MagentoFrameworkSerializeSerializerJson::class);









    share|improve this question

























      1












      1








      1








      Not sure if it is Magento related question. But need to understand this.



      I have seen some of the parameters in construct are assigned to null value.



      For example:



      /**
      * Initialize dependencies.
      *
      * @param MagentoFrameworkModelContext $context
      * @param MagentoFrameworkRegistry $registry
      * @param MagentoFrameworkApiExtensionAttributesFactory $extensionFactory
      * @param AttributeValueFactory $customAttributeFactory
      * @param MagentoSalesModelOrderFactory $orderFactory
      * @param MagentoStoreModelStoreManagerInterface $storeManager
      * @param MagentoCatalogApiProductRepositoryInterface $productRepository
      * @param MagentoFrameworkModelResourceModelAbstractResource $resource
      * @param MagentoFrameworkDataCollectionAbstractDb $resourceCollection
      * @param array $data
      * @param MagentoFrameworkSerializeSerializerJson|null $serializer
      * @SuppressWarnings(PHPMD.ExcessiveParameterList)
      */
      public function __construct(
      MagentoFrameworkModelContext $context,
      MagentoFrameworkRegistry $registry,
      MagentoFrameworkApiExtensionAttributesFactory $extensionFactory,
      AttributeValueFactory $customAttributeFactory,
      MagentoSalesModelOrderFactory $orderFactory,
      MagentoStoreModelStoreManagerInterface $storeManager,
      MagentoCatalogApiProductRepositoryInterface $productRepository,
      MagentoFrameworkModelResourceModelAbstractResource $resource = null,
      MagentoFrameworkDataCollectionAbstractDb $resourceCollection = null,
      array $data = ,
      MagentoFrameworkSerializeSerializerJson $serializer = null
      ) {
      parent::__construct(
      $context,
      $registry,
      $extensionFactory,
      $customAttributeFactory,
      $resource,
      $resourceCollection,
      $data
      );
      $this->serializer = $serializer ?: MagentoFrameworkAppObjectManager::getInstance()
      ->get(MagentoFrameworkSerializeSerializerJson::class);
      $this->_orderFactory = $orderFactory;
      $this->_storeManager = $storeManager;
      $this->productRepository = $productRepository;
      }


      MagentoFrameworkSerializeSerializerJson $serializer = null is assigned to null. And in the function it is assigned to object.



      $this->serializer = $serializer ?: MagentoFrameworkAppObjectManager::getInstance()
      ->get(MagentoFrameworkSerializeSerializerJson::class);









      share|improve this question














      Not sure if it is Magento related question. But need to understand this.



      I have seen some of the parameters in construct are assigned to null value.



      For example:



      /**
      * Initialize dependencies.
      *
      * @param MagentoFrameworkModelContext $context
      * @param MagentoFrameworkRegistry $registry
      * @param MagentoFrameworkApiExtensionAttributesFactory $extensionFactory
      * @param AttributeValueFactory $customAttributeFactory
      * @param MagentoSalesModelOrderFactory $orderFactory
      * @param MagentoStoreModelStoreManagerInterface $storeManager
      * @param MagentoCatalogApiProductRepositoryInterface $productRepository
      * @param MagentoFrameworkModelResourceModelAbstractResource $resource
      * @param MagentoFrameworkDataCollectionAbstractDb $resourceCollection
      * @param array $data
      * @param MagentoFrameworkSerializeSerializerJson|null $serializer
      * @SuppressWarnings(PHPMD.ExcessiveParameterList)
      */
      public function __construct(
      MagentoFrameworkModelContext $context,
      MagentoFrameworkRegistry $registry,
      MagentoFrameworkApiExtensionAttributesFactory $extensionFactory,
      AttributeValueFactory $customAttributeFactory,
      MagentoSalesModelOrderFactory $orderFactory,
      MagentoStoreModelStoreManagerInterface $storeManager,
      MagentoCatalogApiProductRepositoryInterface $productRepository,
      MagentoFrameworkModelResourceModelAbstractResource $resource = null,
      MagentoFrameworkDataCollectionAbstractDb $resourceCollection = null,
      array $data = ,
      MagentoFrameworkSerializeSerializerJson $serializer = null
      ) {
      parent::__construct(
      $context,
      $registry,
      $extensionFactory,
      $customAttributeFactory,
      $resource,
      $resourceCollection,
      $data
      );
      $this->serializer = $serializer ?: MagentoFrameworkAppObjectManager::getInstance()
      ->get(MagentoFrameworkSerializeSerializerJson::class);
      $this->_orderFactory = $orderFactory;
      $this->_storeManager = $storeManager;
      $this->productRepository = $productRepository;
      }


      MagentoFrameworkSerializeSerializerJson $serializer = null is assigned to null. And in the function it is assigned to object.



      $this->serializer = $serializer ?: MagentoFrameworkAppObjectManager::getInstance()
      ->get(MagentoFrameworkSerializeSerializerJson::class);






      magento2






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 3 hours ago









      Adarsh KhatriAdarsh Khatri

      6,73511644




      6,73511644






















          1 Answer
          1






          active

          oldest

          votes


















          3














          This is done for backward compatibility. For instance, if a class was inherited and the child class doesn't specify the needed argument the class initialization doesn't fail, the missed dependency will be initialized by ObjectManager.



          Such workaround was added in Magento 2.2.0 release when all public code was marked as @api to don't break extensions which might use the private code. Starting from 2.2.0, the code which not marked as @api might be changed in a patch release and it won't be a breaking change because other classes should not depend on the private implementation.



          For more details, please, see Adding a constructor parameter section in the official documentation.






          share|improve this answer
























          • That make sense now. Thanks.

            – Adarsh Khatri
            45 mins ago











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "479"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f262738%2fwhat-is-the-benefit-of-assigning-null-to-some-parameters-in-construct%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          3














          This is done for backward compatibility. For instance, if a class was inherited and the child class doesn't specify the needed argument the class initialization doesn't fail, the missed dependency will be initialized by ObjectManager.



          Such workaround was added in Magento 2.2.0 release when all public code was marked as @api to don't break extensions which might use the private code. Starting from 2.2.0, the code which not marked as @api might be changed in a patch release and it won't be a breaking change because other classes should not depend on the private implementation.



          For more details, please, see Adding a constructor parameter section in the official documentation.






          share|improve this answer
























          • That make sense now. Thanks.

            – Adarsh Khatri
            45 mins ago
















          3














          This is done for backward compatibility. For instance, if a class was inherited and the child class doesn't specify the needed argument the class initialization doesn't fail, the missed dependency will be initialized by ObjectManager.



          Such workaround was added in Magento 2.2.0 release when all public code was marked as @api to don't break extensions which might use the private code. Starting from 2.2.0, the code which not marked as @api might be changed in a patch release and it won't be a breaking change because other classes should not depend on the private implementation.



          For more details, please, see Adding a constructor parameter section in the official documentation.






          share|improve this answer
























          • That make sense now. Thanks.

            – Adarsh Khatri
            45 mins ago














          3












          3








          3







          This is done for backward compatibility. For instance, if a class was inherited and the child class doesn't specify the needed argument the class initialization doesn't fail, the missed dependency will be initialized by ObjectManager.



          Such workaround was added in Magento 2.2.0 release when all public code was marked as @api to don't break extensions which might use the private code. Starting from 2.2.0, the code which not marked as @api might be changed in a patch release and it won't be a breaking change because other classes should not depend on the private implementation.



          For more details, please, see Adding a constructor parameter section in the official documentation.






          share|improve this answer













          This is done for backward compatibility. For instance, if a class was inherited and the child class doesn't specify the needed argument the class initialization doesn't fail, the missed dependency will be initialized by ObjectManager.



          Such workaround was added in Magento 2.2.0 release when all public code was marked as @api to don't break extensions which might use the private code. Starting from 2.2.0, the code which not marked as @api might be changed in a patch release and it won't be a breaking change because other classes should not depend on the private implementation.



          For more details, please, see Adding a constructor parameter section in the official documentation.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 1 hour ago









          joni jonesjoni jones

          1,808414




          1,808414













          • That make sense now. Thanks.

            – Adarsh Khatri
            45 mins ago



















          • That make sense now. Thanks.

            – Adarsh Khatri
            45 mins ago

















          That make sense now. Thanks.

          – Adarsh Khatri
          45 mins ago





          That make sense now. Thanks.

          – Adarsh Khatri
          45 mins ago


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Magento Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f262738%2fwhat-is-the-benefit-of-assigning-null-to-some-parameters-in-construct%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          SQL Server 17 - Attemping to backup to remote NAS but Access is denied

          Always On Availability groups resolving state after failover - Remote harden of transaction...

          Restoring from pg_dump with foreign key constraints