Timeline for Return custom db fields via graphql resolvers
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 8, 2022 at 11:44 | vote | accept | Herokiller | ||
| May 31, 2022 at 11:57 | comment | added | Siarhey Uchukhlebau |
@Herokiller If use of the deprecated customerOrders query is required I'll recommend you to create an around plugin for Magento\SalesGraphQl\Model\Resolver\Orders::resolve and fully rewrite this method, but it is strongly not recommended.
|
|
| May 31, 2022 at 11:50 | comment | added | Siarhey Uchukhlebau |
@Herokiller in the vendor/magento/module-sales-graph-ql/Model/Resolver/CustomerOrders.php Magento formatting all orders using this line of code: $ordersArray[] = $this->orderFormatter->format($orderModel); and Inside it adds an Order model to each entity.
|
|
| May 31, 2022 at 11:44 | comment | added | Herokiller | where does $value['model'] come from? it's empty in my case | |
| May 31, 2022 at 11:40 | history | edited | Siarhey Uchukhlebau | CC BY-SA 4.0 |
added 2316 characters in body
|
| May 31, 2022 at 11:34 | history | answered | Siarhey Uchukhlebau | CC BY-SA 4.0 |