-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to retrieve comments on Orders/Shipments/Invoices #39630
Comments
Hi @paales. Thank you for your report.
Join Magento Community Engineering Slack and ask your questions in #github channel. |
Hi @engcom-Delta. Thank you for working on this issue.
|
Hi @paales , Thanks for your reporting and collaboration. Steps to reproduce :
Kindly recheck the issue in Latest 2.4-develop instance and elaborate the steps to reproduce if the issue is still reproducible. Thanks. |
Preconditions and environment
Steps to reproduce
Make sure you have given the correct order number that you placed, so pass variables:
Also make sure you have the correct headers (replace the values with the correct values):
Expected result
I would expect customer.orders.items.0.comments to be an array
I would expect customer.orders.items.0.comments.0 to have a value
I would expect customer.orders.invoices.0.comments.0 to have a values
I would expect customer.orders.shipments.0.comments.0 to have a values
Actual result
Additional information
Credit memo has a resolver (so that one works):
magento2/app/code/Magento/SalesGraphQl/etc/schema.graphqls
Lines 254 to 260 in 4e99810
Order has no resolver for comments:
magento2/app/code/Magento/SalesGraphQl/etc/schema.graphqls
Lines 59 to 86 in 4e99810
Invoice:
magento2/app/code/Magento/SalesGraphQl/etc/schema.graphqls
Lines 173 to 179 in 4e99810
Shipment:
magento2/app/code/Magento/SalesGraphQl/etc/schema.graphqls
Lines 217 to 223 in 4e99810
Release note
GraphQ: While quering for comments on orders, shipments or invoices it would return en empty array, now it returns the actual comments.
Triage and priority
The text was updated successfully, but these errors were encountered: