PaymentServicesPaypal module implicitly depends on InventoryInStorePickupFrontend module and breaks the checkout

[martin-cod]

Preconditions and environment

• Magento version 2.4.7-p8
• Payment Services module version 2.13.0
• Magento_InventoryInStorePickupFrontend module is disabled as well as other Magento_Inventory* modules

Steps to reproduce

1. Add product to cart
2. Go to checkout
3. Fill in shipping information and go to Payment step
4. Review Shipping Information in Order Summary block

Expected result

Shipping Information visible and displays the actual Shipping data as it was on Payment Services module version 2.11.0

Actual result

Shipping Information is empty, JS error in console

Additional information

There is a mixin vendor/magento/module-inventory-in-store-pickup-frontend/view/frontend/web/js/view/shipping-information-ext.js where isStorePickup function is declared. Since Magento_InventoryInStorePickupFrontend module is disabled mixin is not loaded.

Magento_PaymentServicesPaypal module adds another mixin vendor/magento/module-payment-services-paypal/view/frontend/web/js/view/shipping-information-mixin.js and original shipping-information.html template is overwritten. In the template there is a call of <!-- ko if: (!isStorePickup()) --> but function is not found.

So that, Magento_PaymentServicesPaypal module has implicit dependency on logic of Magento_InventoryInStorePickupFrontend module but it has no explicit dependency defined in module.xml

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @martin-cod. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.