ShipmentTracking.title shall not be non-nullable

[jbruni]

Guys... look at this:

magento2/app/code/Magento/SalesGraphQl/etc/schema.graphqls

Line 216 in c893121

title: String! @doc(description: "The shipment tracking title.")

This shouldn't be "non-nullable", because:

• Nothing in the admin prevents from submitting a shipment with empty (null) title. It is not a required field.
• When we query a shipment with empty (null) title through GraphQL, it results in an error:

    "errors": [
        {
            "message": "Internal server error",
            "locations": [
                {
                    "line": 1,
                    "column": 704
                }
            ],
            "path": [
                "customer",
                "orders",
                "items",
                0,
                "shipments",
                0,
                "tracking",
                0,
                "title"
            ],
            "extensions": {
                "debugMessage": "Cannot return null for non-nullable field \"ShipmentTracking.title\"."
            }
        }
    ]

In order to fix this bug locally, I had to overwrite the GraphQL schema definition for ShipmentTracking.title field, making it nullable:

type ShipmentTracking @doc(description: "Contains order shipment tracking details.") {
    title: String @doc(description: "The shipment tracking title.")
}

Please make it nullable so it works for everyone without the need to override.

Thanks!

[m2-assistant]

Hi @jbruni. 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. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• 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-Dash. 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

     - 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!

---

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

[m2-assistant]

Hi @engcom-Delta. 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

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

[engcom-Delta]

Hi @jbruni ,

Thank you for your reporting and collaboration.

We have tried to reproduce the issue on 2.4-develop but we couldn't reproduce this.

Can you provide us the mutation used in graphql to reproduce the issue.

Thanks,

[engcom-Delta]

Hi @jbruni ,

Awaiting your reply to move further on this issue.

Thanks,