Cannot return null for non-nullable field \"AppliedCoupon.code\" unexpected issue

[Dnd-Mafer]

Preconditions and environment

Magento 2.4.8

Steps to reproduce

• Create a salesrule with a specific coupon code available for everyone with a discount amount
• Create a quote
• Apply this coupon
• Place the order
• Get the order using GraphQL with the "applied_coupons.code" node

query getOrderByNumber($orderNumber: String!) {
  customer {
    orders(filter: { number: { eq: $orderNumber } }) {
      items {
        orderNumber: number
        applied_coupons {
          code
        }
      }
    }
  }
}

Expected result

{
  "data": {
    "customer": {
      "orders": {
        "items": [
          {
            "orderNumber": "000000003",
            "applied_coupons": [
              {
                "code": "h20"
              }
            ]
          }
        ]
      }
    }
  }
}

Actual result

{
  "errors": [
    {
      "message": "Internal server error",
      "locations": [
        {
          "line": 7,
          "column": 11
        }
      ],
      "path": [
        "customer",
        "orders",
        "items",
        0,
        "applied_coupons",
        0,
        "code"
      ],
      "extensions": {
        "debugMessage": "Cannot return null for non-nullable field \"AppliedCoupon.code\"."
      }
    }
  ],
  "data": {
    "customer": {
      "orders": {
        "items": [
          {
            "orderNumber": "000000003",
            "applied_coupons": [
              null
            ]
          }
        ]
      }
    }
  }
}

Additional information

Because of \Magento\SalesGraphQl\Model\Formatter\Order::format()

'applied_coupons' => $orderModel->getCouponCode() ? ['code' => $orderModel->getCouponCode()] : []

This should be encapsulate in an array

'applied_coupons' => $orderModel->getCouponCode() ? [['code' => $orderModel->getCouponCode()]] : [],

Release note

GraphQL - fix issue while getting applied_coupons.code on order

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 @Dnd-Mafer. 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.

[Dnd-Mafer]

@magento I am working on this

[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.

[engcom-Bravo]

Hi @Dnd-Mafer,

Thanks for your reporting and collaboration.

We have tried to reproduce the issue in latest 2.4-develop and 2.4.8 instance and we are able to reproduce the issue.Kindly refer the screenshots.

2.4.8

2.4-develop

Hence Confirming the issue.

Thanks.