Closed VZeroCool closed 3 years ago
Hi @VZeroCool. Thank you for your report. To help us process this issue please make sure that you provided the following information:
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.
@VZeroCool do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?
As this is at code level I cant check in instance you are going to provide.
Hi @engcom-Alfa. 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: :point_down:
[ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).Details
If the issue has a valid description, the label Issue: Format is valid
will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid
appears.
[ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description
label to the issue by yourself.
[ ] 3. Add Component: XXXXX
label(s) to the ticket, indicating the components it may be related to.
[ ] 4. Verify that the issue is reproducible on 2.4-develop
branchDetails
- 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.
Hi @VZeroCool . Thank you for your report. It is expected behavior. If you do the following:
$this->orderRepository->get($orderId)
- it returns order object
and order has this method:
\Magento\Sales\Model\Order::getShippingAddress
Also, you can following this scenario ( it is the same):
1) $order = $this->orderRepository->get($orderId)
2) $address = $order->getShippingAddress()
Actual Result: :heavy_check_mark: Its returns shipping Address
So, we have to close it. Thanks!
Preconditions (*)
Steps to reproduce (*)
$this->orderRepository->get($orderId)->getShippingAddress()
Expected result (*)
Actual result (*)
Solid confusion going on........