Closed
Description
(i) This ticket is created automatically based on a verified GitHub issue.
{panel}
If you are starting to work on this Jira ticket, please notify issue reporter and authors of related community pull requests (if any) that you are going to work on this issue:
- Assign #30031 issue to yourself on Magento GitHub
- Add comment "Internal Magento team is working on this issue right now."
{panel}
This issue is automatically created based on existing pull request: magento/magento2#: Remove a redundant getMappedNums from a loop #27939: magento/magento2#: Remove a redundant getMappedNums from a loop-------######Preconditions (*) - 2.4-develop
######Description (*)
Removes a redundant getMappedNums
from a loop.
Before changes:
!bef79987364-fc982d80-84b5-11ea-8f6d-d0047b8245fa.png|thumbnail!
After fix:
!aft79987388-028e0e80-84b6-11ea-8005-51fb618b8fb1.png|thumbnail!
######Related Pull Requests
######Fixed Issues (if relevant)
- magento/magento2#<issue_number>: Issue title
######Steps to reproduce (*)
- ...
- ...
######Expected result (*)
...
######Actual result (*)
######Questions or comments
######Contribution checklist (*)
- < ] Pull request has a meaningful description of its purpose
- All commits are accompanied by meaningful commit messages
- All new or changed code is covered with unit/integration tests (if applicable)
- [ > All automated tests passed successfully (all builds are green)
Metadata
Metadata
Assignees
Labels
GraphQLThe issue has been fixed in 2.4-develop branchGate 3 Passed. Manual verification of the issue completed. Issue is confirmedGate 1 Passed. Automatic verification of issue format passedGate 4. Acknowledged. Issue is added to backlog and ready for developmentA defect with this priority could have functionality issues which are not to expectations.Indicates original Magento version for the Issue report.The issue has been reproduced on latest 2.4-develop branchAffects non-critical data or functionality and does not force users to employ a workaround.
Type
Projects
Status
Done