[Issue] [Feature request] Add paypal_express_visible_on_cart & paypal_express_active in graphql StoreConfig

magento / magento2

Prior to making any Submission(s), you must sign an Adobe Contributor License Agreement, available here at: https://opensource.adobe.com/cla.html. All Submissions you make to Adobe Inc. and its affiliates, assigns and subsidiaries (collectively “Adobe”) are subject to the terms of the Adobe Contributor License Agreement.

Open Software License 3.0

11.47k stars 9.28k forks source link

This issue is automatically created based on existing pull request: magento/magento2#39163: [Feature request] Add paypal_express_visible_on_cart & paypal_express_active in graphql StoreConfig

Description (*)

This PR add paypal_express_visible_on_cart and paypal_express_active in graphQl StoreConfig type.

:+1: I think, is important to prefix configuration by theme (ie: paypal) - So payment_payflowpro_cc_vault_active must be replaced by paypal_payment_payflowpro_cc_vault_active ...

query StoreConfig {
  storeConfig {
    paypal_express_active
    paypal_express_visible_on_cart
  }
}

Related Pull Requests

None

Fixed Issues (if relevant)

None

Manual testing scenarios (*)

Setup PayPal and execute following graphql query :

query StoreConfig {
  storeConfig {
    paypal_express_active
    paypal_express_visible_on_cart
  }
}

Contribution checklist (*)

[ ] Pull request has a meaningful description of its purpose
[x] All commits are accompanied by meaningful commit messages
[x] All new or changed code is covered with unit/integration tests (if applicable)
[x] README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
[ ] All automated tests passed successfully (all builds are green)

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: :point_down:

[ ] 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
- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
- 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.

magento / magento2