-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Exception are not translated to store scope #32953
Exception are not translated to store scope #32953
Conversation
Hi @rikwillems. Thank you for your contribution
❗ Automated tests can be triggered manually with an appropriate comment:
You can find more information about the builds here ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review. For more details, please, review the Magento Contributor Guide documentation. 🕙 You can find the schedule on the Magento Community Calendar page. 📞 The triage of Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket. 🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel ✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel |
@magento run all tests |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time. |
@magento run Functional Tests B2b, WebAPI Tests |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time. |
@magento run Semantic Version Checker |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rikwillems Thanks for your contribution.
Please look at my comments and update adding of new constructor params based on Backward Compatibility Policy
@@ -114,7 +121,8 @@ public function __construct( | |||
QueryFields $queryFields, | |||
JsonFactory $jsonFactory = null, | |||
HttpResponse $httpResponse = null, | |||
ContextFactoryInterface $contextFactory = null | |||
ContextFactoryInterface $contextFactory = null, | |||
AreaList $areaList |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AreaList $areaList | |
AreaList $areaList = null |
@@ -127,6 +135,7 @@ public function __construct( | |||
$this->jsonFactory = $jsonFactory ?: ObjectManager::getInstance()->get(JsonFactory::class); | |||
$this->httpResponse = $httpResponse ?: ObjectManager::getInstance()->get(HttpResponse::class); | |||
$this->contextFactory = $contextFactory ?: ObjectManager::getInstance()->get(ContextFactoryInterface::class); | |||
$this->areaList = $areaList; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
$this->areaList = $areaList; | |
$this->areaList = $areaList ?: ObjectManager::getInstance()->get(AreaList::class); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please see the updated PR.
@magento run all tests |
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time. |
There is a internal PR ticket raised on this same issue and that is being processed. |
Hi @engcom-Alfa or @cpartica: is there any news around this? It's kind of annoying that this public issue got closed and replaced by a private issue that the community can not see into, it would be nice if you stopped doing this in the future, thanks! |
The effect is because of the process we have. Please don't update the branch or add any new commits or it will not automerge |
Hi @rikwillems. Thank you for your contribution
❗ Automated tests can be triggered manually with an appropriate comment:
You can find more information about the builds here ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review. For more details, review the Magento Contributor Guide documentation. 🕙 You can find the schedule on the Magento Community Calendar page. 📞 The triage of Pull Requests 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. ✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel |
#31351
Description (*)
Related Pull Requests
magento/inventory#3318
Fixed Issues (if relevant)
Manual testing scenarios (*)
Questions or comments
Contribution checklist (*)