Enter a type and click search.




Results for KPCommandPool

File: vendor/klarna/module-ordermanagement/etc/di.xml

<virtualType name="KPCommandPool"
             type="Magento\Payment\Gateway\Command\CommandPool">
    <arguments>
        <argument name="commands" xsi:type="array">
            <item name="capture" xsi:type="string">
                Klarna\Ordermanagement\Gateway\Command\Capture
            </item>
            <item name="cancel" xsi:type="string">
                Klarna\Ordermanagement\Gateway\Command\Cancel
            </item>
            <item name="void" xsi:type="string">
                Klarna\Ordermanagement\Gateway\Command\Cancel
            </item>
            <item name="refund" xsi:type="string">
                Klarna\Ordermanagement\Gateway\Command\Refund
            </item>
        </argument>
    </arguments>
</virtualType>

This is a virtual type configuration.

This configuration is for the base area. Base area configurations will apply to all the sub-applications.

This virtualType configuration tells the Object Manager when a user wants a virtual KPCommandPool object that it should return a Magento\Payment\Gateway\Command\CommandPool object.

This configuration tells the Object Manager that when a user wants a KPCommandPool object that the following arguments should be used in the foo object's constructor.

  • $commands = [...items...];
Results for KPCommandPool

File: vendor/klarna/module-kp/etc/di.xml

<virtualType name="KPVirtual"
             type="Magento\Payment\Model\Method\Adapter">
    <arguments>
        <argument name="code" xsi:type="const">
            Klarna\Kp\Model\Payment\Kp::METHOD_CODE
        </argument>
        <argument name="valueHandlerPool" xsi:type="object">
            KPValueHandlerPool
        </argument>
        <argument name="commandPool" xsi:type="object">
            KPCommandPool
        </argument>
        <argument name="validatorPool" xsi:type="object">
            KPValidatorPool
        </argument>
        <argument name="formBlockType" xsi:type="string">
            Magento\Payment\Block\Form
        </argument>
        <argument name="infoBlockType" xsi:type="string">
            Klarna\Core\Block\Info\Klarna
        </argument>
    </arguments>
</virtualType>

This is a virtual type configuration.

This configuration is for the base area. Base area configurations will apply to all the sub-applications.

This virtualType configuration tells the Object Manager when a user wants a virtual KPVirtual object that it should return a Magento\Payment\Model\Method\Adapter object.

This configuration tells the Object Manager that when a user wants a KPVirtual object that the following arguments should be used in the foo object's constructor.

  • $code = Klarna\Kp\Model\Payment\Kp::METHOD_CODE;
  • $valueHandlerPool = new KPValueHandlerPool (...)
  • $commandPool = new KPCommandPool (...)
  • $validatorPool = new KPValidatorPool (...)
  • $formBlockType = "Magento\Payment\Block\Form";
  • $infoBlockType = "Klarna\Core\Block\Info\Klarna";

File: vendor/klarna/module-kp/etc/di.xml

<virtualType name="KPCommandPool"
             type="Magento\Payment\Gateway\Command\CommandPool">
    <arguments>
        <argument name="commands" xsi:type="array">
            <item name="authorize" xsi:type="string">
                Klarna\Kp\Gateway\Command\Authorize
            </item>
        </argument>
    </arguments>
</virtualType>

This is a virtual type configuration.

This configuration is for the base area. Base area configurations will apply to all the sub-applications.

This virtualType configuration tells the Object Manager when a user wants a virtual KPCommandPool object that it should return a Magento\Payment\Gateway\Command\CommandPool object.

This configuration tells the Object Manager that when a user wants a KPCommandPool object that the following arguments should be used in the foo object's constructor.

  • $commands = [...items...];