Bundle product with option type radio and dropdown can be added to the cart with multiple choices

[TomashKhamlai]

Preconditions (*)

1. Sample Data

Steps to reproduce (*)

1. Add product to the cart

mutation addBundle(
  $cart_id: String!
) {
  addBundleProductsToCart(
    input: {
      cart_id: $cart_id
      cart_items: {
        data: {
          quantity: 1
          sku: "24-WG080"
        }
        bundle_options: [
          {
            id: 1
            quantity: 1
            value: [
              "1"
              "2"
              "3"
            ]
          }
          {
            id: 2
            quantity: 1
            value: [
              "4"
            ]
          }
                    {
            id: 3
            quantity: 1
            value: [
              "5"
            ]
          }
                    {
            id: 4
            quantity: 1
            value: [
              "8"
            ]
          }
        ]
      }
    }
  ) {
    cart {
      items {
        id
        quantity
        product {
          sku
        }
        ... on BundleCartItem {
          bundle_options {
            id
            label
            type
            values {
              id
              label
              quantity
              __typename
            }
          }
        }
      }
    }
  }
}

Expected result (*)

1. Some message that complains about invalid input for BundleItem.type: radio/dropdown

Actual result (*)

1. Successfully added to cart

Additional information

The issue was confirmed again on the lates 2.4-develop code. May 28, 2020
In general it is possible to add to Shopping Cart and place order with option type radio and dropdown with multiple choices. This flow is not possible using UI on Storefront.
More details: #26110 (comment)

[sedonik]

Hi @TomashKhamlai,

There were not be able to reproduce.
There is an error:

Magento\\\\Framework\\\\GraphQl\\\\Schema\\\\Type\\\\Output\\\\ElementMapper\\\\Format' in '\\/var\\/www\\/magento2\\/graphql\\/pub\\/lib\\/internal\\/Magento\\/Framework\\/GraphQl\\/Schema\\/Type\\/ScalarTypes.php' on line 23\",\"trace\":\"Trace is not available.\"}]}}"

Was tested in magento/graphql-ce branch: 2.3-develop

Could you advise?

[TomashKhamlai]

I will try.

[sedonik]

Hi @TomashKhamlai,

Sorry, I've made:

composer install

and

composer update

and this Error was gone.
Continue investigating.

[m2-assistant]

Hi @TomashKhamlai. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

@TomashKhamlai do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[magento-engcom-team]

✅ Confirmed by @lenaorobei
Thank you for verifying the issue. Based on the provided information internal tickets MC-29908 were created

Issue Available: @lenaorobei, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[m2-assistant]

Hi @sedonik. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 2. 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!

• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[sedonik]

Hi @lenaorobei,

I've created PR #26122
Could you check is it implemented correctly?

Thanks.

[lenaorobei]

@magento give me 2.4-develop instance

[magento-engcom-team]

Hi @lenaorobei. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @lenaorobei, here is your Magento instance.
Admin access: https://i-26110-2-4-develop.instances.magento-community.engineering/admin_7b6b
Login: 79ed051f Password: 9a178b5c48e9
Instance will be terminated in up to 3 hours.

[chalov-anton]

Rechecked on the latest Magento 2.4-develop

The issue is still reproducible.
I can successfully perform the following mutations:

1. addBundleProductsToCart
2. setBillingAddressOnCart
3. setShippingAddressesOnCart
4. setShippingMethodsOnCart
5. setPaymentMethodOnCart 

and Place the order

mutation {
  placeOrder(input: {cart_id: "AgfUXQZms2gu5SUTPHRvisT8VnzPLdF5"}) {
    order {
      order_number
    }
  }
}

response: 
{
  "data": {
    "placeOrder": {
      "order": {
        "order_number": "000000003"
      }
    }
  }
}

The order is created in Admin Panel

Admin can successfully:

1. Send Email
2. Invoice
3. Ship
   and Complete the order
   

[m2-assistant]

Hi @danielrenaud. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
• 2. 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!
• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant]

Hi @michalderlatka. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
• 2. 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!
• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.