What is the benefit of assigning null to some parameters in construct?Unit Test for overwrite collection...

Why does finding small effects in large studies indicate publication bias?

How to write painful torture scenes without being over-the-top

Is Apex Sometimes Case Sensitive?

Ramanujan's radical and how we define an infinite nested radical

How bad is a Computer Science course that doesn't teach Design Patterns?

What dissuades people from lying about where they live in order to reduce state income taxes?

What happens if you declare more than $10,000 at the US border?

How to not forget my phone in the bathroom?

Is Screenshot Time-tracking Common?

Is layered encryption more secure than long passwords?

Automated testing of chained Queueable jobs in Salesforce

Why is ra lower than re while la is higher than le?

Can I use a larger HVAC Hard Start kit than is recommended?

How would a coma-like death system work on an alien world?

How do I write a maintainable, fast, compile-time bit-mask in C++?

Using 14 ga on part of a 20A circuit?

Boiling meatballs, how long?

How can I make my enemies feel real and make combat more engaging?

Do all Half-Elf subraces forgo the Skill Versatility feature?

Sauna: Wood does not feel so hot

Truncating the output of AES-128

Portent, as it relates to the Gambling downtime rules from Xanathar's Guide to Everything

How do I add a strong "onion flavor" to the biryani (in restaurant style)?

How do sapient birds/theropods build their seats?



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


Unit Test for overwrite collection class in magento2Model Override issue in magento 2Magento 2: Plugin class does not existUnable to create order from admin in magento 2PHP fatal error: Uncaught TypeError: Argument 2 passed to MagentoCatalogPluginBlockTopmenuMagento2 REST API get all customers detailsPHP Fatal error: Uncaught TypeError: Argument 1 passed to Magento\Framework\Data\Collection\AbstractDb::setConnection() must implement interfaceMagento 2 ErrorIncompatible argument type error during compilation in Magento2.2.5?get invoice item using order_item_id in magento 2













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
            43 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
            43 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
            43 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
            43 mins ago



















          • That make sense now. Thanks.

            – Adarsh Khatri
            43 mins ago

















          That make sense now. Thanks.

          – Adarsh Khatri
          43 mins ago





          That make sense now. Thanks.

          – Adarsh Khatri
          43 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

          Anexo:Material bélico de la Fuerza Aérea de Chile Índice Aeronaves Defensa...

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

          update json value to null Announcing the arrival of Valued Associate #679: Cesar Manara ...