-
Notifications
You must be signed in to change notification settings - Fork 9.4k
Improving the code readability by importing the classes #33168
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
base: 2.4-develop
Are you sure you want to change the base?
Conversation
Hi @tiagosampaio. 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 all |
Failed to run the builds. Please try to re-run them later. |
@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. |
Pull Requests are not mergeable to the mainline. Please merge the latest mainlines to your Pull Requests and restart the builds. |
@tiagosampaio , Please resolve the conflict on the PR to move ahead on this. |
@magento run all tests |
@magento run Functional Tests B2B |
Honestly, I find that this doesn't improve readability at all, like when you see I think proper aliases should be used if the claim is to improve readability, for example: use Magento\Framework\Event\ManagerInterface as EventManagerInterface; And next to
(I maybe have missed some, naming things is hard, I know) |
Thank you @hostep for the input. I have made the changes as you suggested. |
@magento run all tests |
As the PR is to improve code quality, manual testing is not applicable. Since the builds are failed moving this to Extended testing. |
@magento run all tests |
* @param string $fieldId Need for support of clone_field feature | ||
* @param array $oldConfig Need for compatibility with _processGroup() | ||
* @param array $extraOldGroups Need for compatibility with _processGroup() | ||
* @return string | ||
*/ | ||
private function getFieldPath(Field $field, string $fieldId, array &$oldConfig, array &$extraOldGroups): string | ||
private function getFieldPath(FieldElement $field, string $fieldId, array &$oldConfig, array &$extraOldGroups): string // phpcs:ignore Generic.Files.LineLength |
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.
Let's not ignore the coding standards.
private function getFieldPath(FieldElement $field, string $fieldId, array &$oldConfig, array &$extraOldGroups): string // phpcs:ignore Generic.Files.LineLength | |
private function getFieldPath( | |
FieldElement $field, | |
string $fieldId, | |
array &$oldConfig, | |
array &$extraOldGroups | |
): string |
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.
Have made changes as you suggested.
@magento run all tests |
Since there is a SVC failure, we have raised a internal approval jira. |
Description (*)
Improving the code readability by importing the classes.
Related Pull Requests
Fixed Issues (if relevant)
Manual testing scenarios (*)
Questions or comments
Contribution checklist (*)